You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Vamsi-klu (via GitHub)" <gi...@apache.org> on 2026/06/22 02:37:13 UTC

Re: [PR] Fix KubernetesExecutor retry losing hostname [airflow]

Vamsi-klu commented on PR #67372:
URL: https://github.com/apache/airflow/pull/67372#issuecomment-4764226418

   This still misses the scheduler executor-event path that triggers the KubernetesExecutor symptom. A failed executor event for a TI still in `SCHEDULED`/`QUEUED` enters the state-mismatch path, then calls `ti.handle_failure()`. But `handle_failure()` only records history when `ti.state == RUNNING`; otherwise it sets `UP_FOR_RETRY` without `prepare_db_for_next_try()`. Please add/fix the scheduler executor-event retry path and add a regression test where a non-running queued/scheduled TI receives a failed executor event and preserves `TaskInstanceHistory.hostname`/`start_date`.


-- 
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