repl-chris commented on PR #23432: URL: https://github.com/apache/airflow/pull/23432#issuecomment-1123148412
> I’m either misunderstanding this or it’s not accurate. At least, there is a `orphaned_tasks_check_interval` and in our experience it gets used. Oooh yes, you're absolutely correct. I had the blinders on and was only looking at the "adopted task timeout" functionality of the celery executor - I totally forgot about the actual orphaned task adoption functionality of the scheduler 😂 > You might try to look at `app.control.inspect().reserved` for tasks that got reserved but didn’t make it to a worker process. Thanks for the tip...I'll look into this a little further but I'm pretty sure they won't be there. My understanding is that reserved tasks will eventually get re-delivered to a different worker after [6 hours](https://github.com/apache/airflow/blob/main/airflow/config_templates/default_celery.py#L37), but I've had tasks stuck for far longer than that...and I did also verify that the stuck tasks did not exist in the `unacked` redis list (which I'd expect is the data source for `inspect().reserved`). Never-the-less I will dig into this a little further, thanks! :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
