Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random failed tasks with no operator and no hostname? #65

Open
7yl4r opened this issue May 25, 2018 · 1 comment
Open

Random failed tasks with no operator and no hostname? #65

7yl4r opened this issue May 25, 2018 · 1 comment
Labels

Comments

@7yl4r
Copy link
Member

7yl4r commented May 25, 2018

I can't see any pattern here, and I have seen this in multiple DAGs since upgrading to v1.9.0.


Here are some "Task Instance Attributes" from the "task instance details view" that may be relevant:

attribute value
Dagrun Running Task instance's dagrun was not in the 'running' state but in the state 'failed'.
Execution Date The execution date is 2002-07-13T19:05:00 but this is before the task's start date 2018-05-25T16:45:25.575395.
is_premature False
max_tries 10
metadata MetaData(bind=None)
next_try_number 1
operator None
pid None
pool None
previous_ti None
queue default
queued_dttm None
start_date None
unixname root

Here is a list of the ones I am clearing from the myd01 proc DAG:

image

@7yl4r 7yl4r added the bug label May 25, 2018
@7yl4r
Copy link
Member Author

7yl4r commented May 25, 2018

Potentially relevant issue: AIRFLOW-695 (fix was merged 2017-01)... so we shouldn't be seeing this in v1.9 (released 2017-12)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant