sidshas03 commented on PR #63355: URL: https://github.com/apache/airflow/pull/63355#issuecomment-4042087335
> > When task runner sends final SUCCESS, if API replies with 409 invalid_state and previous_state=success, we now treat it as duplicate/idempotent state update and do not fail the task process. > > Did you find out why did it errror with 409 invalid state in the first place. Yes, I checked this from my side. 409 invalid_state is coming when same TI gets terminal `SUCCESS` update more than once. In this case, by the time task runner sends final SUCCESS, DB already has SUCCESS (`previous_state=success`), so API rejects the second write. So issue is race/idempotency in state update flow, not wrong task result. So, this PR only handles that exact duplicate success path as no-op, so task process won’t fail for this case. Other invalid_state conflicts are still raised as before. I’m also checking which path is writing first in HA (scheduler side vs worker retry path). If I get clean reproducible logs, I’ll add them in follow-up. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
