airflow
airflow copied to clipboard
Increment try_number while clearing deferred tasks.
closes: #38735 related: #38735
This is already done while marking tasks as success/failure. Should this be done for up_for_reschedule tasks too? See also https://github.com/apache/airflow/pull/30669
https://github.com/apache/airflow/blob/d03ba594b3158c127c1c1b3f1d0c31fb93104367/airflow/api/common/mark_tasks.py#L161-L164
cc: @dstandish
this should be obsoleted by this PR https://github.com/apache/airflow/pull/39336
i'm just working through bunch of test fixes cus we make a lot of assertions about try_number because it's always been so problematic
i would suggest we close this one
@dstandish I agree the linked PR is a good long term solution but this PR is good enough for a bugfix in 2.9.x series with 2.10 release few months away.
@dstandish I agree the linked PR is a good long term solution but this PR is good enough for a bugfix in 2.9.x series with 2.10 release few months away.
Sure no problem
@tirkarthi @dstandish do we want to merge this PR for 2.9.2?
@tirkarthi @dstandish do we want to merge this PR for 2.9.2?
@eladkal I think we cannot merge this anymore now that https://github.com/apache/airflow/pull/39336 is merged. At least not into main. I think the only way this could be released is if it's patched on a 2.9.2 branch specifically. WDYT?
Then its up to @ephraimbuddy I think the real question here is if do we think there is value? If so then @tirkarthi will need to change the base branch of this PR from main to v2.9 stable
Then its up to @ephraimbuddy I think the real question here is if do we think there is value? If so then @tirkarthi will need to change the base branch of this PR from main to v2.9 stable
We can only PR it to v2-9-test but not stable. However, we don't usually do that. We only PR against the test branch if we have issues during the release process and it's mostly CI changes. cc @potiuk
I am okay with closing this since main has a long term fix and 2.10 will be released in few months hopefully. We had this patch since we found this during our upgrade to 2.7.0 using deferrable operators and the patch has been working well.
Yeah. 2.10 is not that far away - and until then @tirkarthi can simply run their forked Airlfow until they upgrade to 2.10.