jscheffl commented on issue #35773: URL: https://github.com/apache/airflow/issues/35773#issuecomment-1872282379
I would assess from the information that this is not a general bug, it is not common. Root cause could be a infrastructure or deployment problem such that local executor was not able to write results to database and as such a second attempt to run again was triggered even though the first run already was successful. It is hard to see this from the logs captured, follow-up errors only show-up on the stdout of the worker node. There was an improvement in Airflow 2.8.0 such that further worker logs are also added to task logs, this increases the probability to see infrastructure errors on this level in task logs. Is there a way to reproduce this problem deterministically? Can you try with 2.8.0 if the problem still persists? -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
