GitHub user GustavoBuosi edited a comment on the discussion: Trying to understand if Race Condition caused by creation of duplicated Task Attempts in Kubernetes Executor is already solved
Hello @UnknownHawkins , thank you for the reply. I have confirmed these are the versions we indeed have in our cluster. While I do understand significant changes were made and should have been addressed in Airflow 2.7.3, from what I've seen they still were occurring in Airflow 3 (as the PR you have shared mentions 3.1.6). There is a recently merged PR that handles other race conditions observed by users #60330, and it looks like it could tackle the error we have reported - however, its milestone is for Airflow 3.3.0 (a currently unreleased version today), and I am not sure it would prevent the bug reported. If I my understanding is correct, #60330 **may** have fixed the reported error (`test_schedule_tis_empty_operator_is_noop_if_ti_already_running` seems to partially simulate it), but the fix would be available on 3.3.0. With that, I have two questions: - Could you confirm if what I've said makes sense? - If it does, do you think it's worth it to at least write a unit test that tries to replicate my case? I would be happy to contribute to the project opening a PR with my colleagues. GitHub link: https://github.com/apache/airflow/discussions/68071#discussioncomment-17506918 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
