You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "dstandish (via GitHub)" <gi...@apache.org> on 2024/11/18 16:08:49 UTC
[I] Executor state mismatch / task killed externally [airflow]
dstandish opened a new issue, #44151:
URL: https://github.com/apache/airflow/issues/44151
### Body
Users have long been confused by log messages along the lines of "task state changed externally", or something about executor state mismatch, where the thing that emits the log is essentially saying, 🤷 , no clue what happened sorry.
E.g. see here https://airflow.apache.org/docs/apache-airflow/stable/troubleshooting.html#task-state-changed-externally
This should mostly be avoidable.
If a task was killed by external user action, why do we not have a signal of that recorded somewhere, and why can't the executor (or task process or whatever) _see_ that and then either not have to log such a message, or log a more helpful one that says exactly what happened.
### Committer
- [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project.
--
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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org