[
https://issues.apache.org/jira/browse/AIRFLOW-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572886#comment-16572886
]
John Cheng edited comment on AIRFLOW-2416 at 8/8/18 8:42 AM:
-------------------------------------------------------------
It's not fixed completely. I try to change the executor_config in my DAG and
clear the task status. However, the new task instance didn't pick up the new
value.
I try to look into the DB and found that task_instance.executor_config is not
cleared when I clear the task status.
was (Author: johnchenghk01):
It's not fixed yet. I try to change the executor_config in my DAG and clear the
task status. However, the new task instance didn't pick up the new value.
I try to look into the DB and found that task_instance.executor_config is not
cleared when I clear the task status.
> 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)
