[GitHub] [airflow] thesuperzapper commented on issue #16163: Confusing log for long running tasks: "dependency 'Task Instance Not Running' FAILED: Task is in the running state"

["thesuperzapper (via GitHub)" <gi...@apache.org>]

thesuperzapper commented on issue #16163:
URL: https://github.com/apache/airflow/issues/16163#issuecomment-1445691129

   I am also experiencing this in airflow 2.4.3 with a number of DAGs. 
   
   The `Task is not able to be run` error message is interesting, and people seem to think that this message is displayed when the `AIRFLOW__CELERY_BROKER_TRANSPORT_OPTIONS__VISIBILITY_TIMEOUT` is shorter than the DAGs takes to run, but that is not my reading of [the docs for that config](https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#visibility-timeout), it's more of a celery timeout for the worker to acknowledge a task once it has been assigned.
   
   It seems likely that the logs are lost for really long running celery tasks (perhaps due to the visibility_timeout, I am not sure), so people only see the `Task is not able to be run` error, but something else (likely their code) is deadlocking, they just cant see it.
   
   Has anyone tried setting `execution_timeout` on those tasks, I assume that airflow will eventually mark that task as failed.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org