Only update RTIF for terminal task states#63719
Conversation
|
Needs some thinking about this -- I'm not sure this is the correct behaviour |
|
Thanks, I anticipated that too. Let me come up with a design for that |
|
At the moment, we're observing that the rtif endpoint does not exist for such intermediate try_numbers of the task run and the post-processing is blocked (e.g. uploading of logs to remote logging store & the logs are not available for those initial try_numbers of the task run) due to the Logs from the worker 404 errors we're seeing in the API server |
|
Thanks for sharing that @pankajkoti, I am thinking of a better way to do things |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
|
hi @amoghrajesh, I just filed a new issue #66416 that lists the bare minimum steps required to reproduce this issue outside of Cosmos. This will help when the fix needs to be tested. |
|
I create another PR to return 410 in setting rtif API if the id is stale. The supervisor ignores 410 case, but still raises error for 404. So we don't need to rely on task instance state to update rtif. WDYT? |
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.