Simplify logic to resolve tasks stuck in queued despite stalled_task_timeout by RNHTTR · Pull Request #30108 · apache/airflow

RNHTTR · 2023-03-14T21:13:55Z

closes: #28120
closes: #21225
closes: #28943

Tasks occasionally get stuck in queued and aren't resolved by stalled_task_timeout (#28120). This PR moves the logic for handling stalled tasks to the scheduler and simplifies the logic by marking any task that has been queued for more than scheduler.task_queued_timeout as failed, allowing it to be retried if the task has available retries.

This doesn't require an additional scheduler nor allow for the possibility of tasks to get stuck in an infinite loop of scheduled -> queued -> scheduled ... -> queued as exists in #28943.

collinmcnulty · 2023-03-14T21:29:12Z

For backward compatibility and semver reasons, would making the tasks go to failed be considered a breaking change? I know that behavior was different than the comparable k8s executor behavior and seems a little askew from expectations so it could be considered a bug I guess? And this does cover that case plus more, so that's good.

RNHTTR · 2023-03-14T21:38:56Z

Would appreciate your feedback @okayhooni & @repl-chris !

airflow/jobs/scheduler_job.py

collinmcnulty · 2023-03-14T21:39:18Z

airflow/jobs/scheduler_job.py

Do you need both of these lines? Don't you only want the one wrapped in timers.call_regular_interval

I was following the precedent set by adopt_or_reset_orphaned_tasks (line 858), which runs on scheduler start up and then at a regular interval.

This probably doesn't need to run at startup. Adoption makes sense to do because it's pretty likely that another scheduler just shut down if we have a new one starting, but I don't we have a similar situation here.

uranusjr · 2023-03-15T05:50:35Z

airflow/config_templates/default_airflow.cfg

Is this deprecation reflected in the code base by a DeprecationWarning?

Updated to include DeprecationWarning

we should remove it if no longer needed

Would removing it unnecessarily break backward compatibility?

airflow/jobs/scheduler_job.py

ephraimbuddy · 2023-03-16T20:02:19Z

airflow/jobs/scheduler_job.py

This would affect all executors, not just celery and we have some other settings in kubernetes for pending tasks etc. WDYT?

IMO this is a general problem that applies to both kubernetes & celery executors. The relevant k8s exec setting is worker_pods_queued_check_interval -- I think this can also be handled in the scheduler. I also think this can probably replace task-adoption-timeout

If you agree, i'll remove those configurations as well.

worker_pods_queued_check_interval is similar, but different in that it won't automatically just reset the TI. It first checks to see if the pod exists.

worker_pods_pending_timeout is essentially this same process though. It should probably be deprecated as well (though, not sure how config handles many -> one).

jedcunningham · 2023-03-20T23:01:13Z

airflow/jobs/scheduler_job.py

You don't have to do this manually, Airflow does it for you when you marked it as a deprecated option.

jedcunningham · 2023-03-20T23:14:42Z

airflow/jobs/scheduler_job.py

worker_pods_queued_check_interval is similar, but different in that it won't automatically just reset the TI. It first checks to see if the pod exists.

worker_pods_pending_timeout is essentially this same process though. It should probably be deprecated as well (though, not sure how config handles many -> one).

jedcunningham · 2023-03-20T23:17:18Z

airflow/jobs/scheduler_job.py

This probably doesn't need to run at startup. Adoption makes sense to do because it's pretty likely that another scheduler just shut down if we have a new one starting, but I don't we have a similar situation here.

ashb · 2023-03-21T16:56:55Z

airflow/jobs/scheduler_job.py

I don't see any handling of retry state in this code, we go straight to failed and bypass retry logic (unless I've forgotten how that works?)

Would it be sufficient to call TI.handle_failure()?

It seems like it should be based on my read of TI.handle_failure.

collinmcnulty · 2023-03-27T18:06:06Z

I'm unclear on why task adoption was removed. It covers a whole class of problem, running tasks whose scheduler died, that doesn't seem to be otherwise affected by this PR.

RNHTTR · 2023-03-28T20:47:47Z

Accidentally closed this and nuked my changes. I'll open a new PR or re-open this one.

RNHTTR requested review from XD-DENG, ashb, kaxil and o-nikolas as code owners March 14, 2023 21:13

boring-cyborg bot added the area:Scheduler including HA (high availability) scheduler label Mar 14, 2023

collinmcnulty reviewed Mar 14, 2023

View reviewed changes

uranusjr reviewed Mar 15, 2023

View reviewed changes

RNHTTR force-pushed the main branch from de10899 to 66b35e3 Compare March 15, 2023 14:32

RNHTTR requested review from collinmcnulty and uranusjr and removed request for XD-DENG, ashb, collinmcnulty, kaxil, o-nikolas and uranusjr March 15, 2023 14:33

potiuk force-pushed the main branch from 66b35e3 to 0675d3c Compare March 16, 2023 00:10

ephraimbuddy reviewed Mar 16, 2023

View reviewed changes

airflow/jobs/scheduler_job.py Outdated Show resolved Hide resolved

RNHTTR force-pushed the main branch from 0675d3c to dff2a3a Compare March 16, 2023 14:53

RNHTTR mentioned this pull request Mar 16, 2023

Add handling logic on CeleryExecutor to reschedule task stuck in queued status #28943

Closed

ephraimbuddy reviewed Mar 16, 2023

View reviewed changes

jedcunningham reviewed Mar 20, 2023

View reviewed changes

ashb reviewed Mar 21, 2023

View reviewed changes

RNHTTR requested a review from dstandish as a code owner March 24, 2023 21:21

RNHTTR closed this Mar 28, 2023

RNHTTR force-pushed the main branch from c20613c to 04be4c0 Compare March 28, 2023 20:26

RNHTTR mentioned this pull request Mar 30, 2023

Simplify logic to resolve tasks stuck in queued despite stalled_task_timeout #30375

Merged

Conversation

RNHTTR commented Mar 14, 2023

Uh oh!

collinmcnulty commented Mar 14, 2023

Uh oh!

RNHTTR commented Mar 14, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ashb Mar 21, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

collinmcnulty commented Mar 27, 2023

Uh oh!

RNHTTR commented Mar 28, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

RNHTTR commented Mar 14, 2023 •

edited

Loading

ashb Mar 21, 2023 •

edited

Loading

RNHTTR commented Mar 28, 2023 •

edited

Loading