You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Cameron Moberg (JIRA)" <ji...@apache.org> on 2018/08/02 17:24:00 UTC
[jira] [Commented] (AIRFLOW-2416) executor_config column in
task_instance isn't getting created
[ https://issues.apache.org/jira/browse/AIRFLOW-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567121#comment-16567121 ]
Cameron Moberg commented on AIRFLOW-2416:
-----------------------------------------
Appears to be fixed in 1.10.0 with this commit.
https://github.com/apache/incubator-airflow/commit/c0920efc012468681cff3d3c9cfe25c7381dc976#diff-2a9d71ae3b365845596dbeef6ec0a17e
> executor_config column in task_instance isn't getting created
> -------------------------------------------------------------
>
> Key: AIRFLOW-2416
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2416
> Project: Apache Airflow
> Issue Type: Bug
> Components: db
> Affects Versions: 1.9.0
> Environment: Running on a mac (System Version: OS X 10.11.6 (15G19009)) dev environment with Python 3.6.
> Reporter: Curtis Deems
> Assignee: Cameron Moberg
> Priority: Major
>
> There's a new column called 'executor_config' in the 'task_instance' table that the scheduler is attempting to query. The column isn't created with initdb or upgradedb so the scheduler just loops and never picks up any dag objects. The only way I discovered this was to run the scheduler thru the debugger and review the exceptions thrown by the scheduler. This issue doesn't show up in the scheduler logs or any other output that I could see.
> The workaround is to create the column manually but since the root issue is not easily discoverable this could be a blocker for some people.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)