scaoupgrade commented on issue #39717: URL: https://github.com/apache/airflow/issues/39717#issuecomment-2269863782
> I'm a noob, but I can follow instructions 😂 Unfortuntly I only have tomorrow to make ot happen has I'm going on vacation!💪💪💪 A segunda, 5/08/2024, 20:45, Jarek Potiuk ***@***.***> escreveu: > […](#) > I can easily close the issue and add simple instructions what anyone who sees similar issue should do (apply patch and if they see similar issue - report all the details there). — Reply to this email directly, view it on GitHub <[#39717 (comment)](https://github.com/apache/airflow/issues/39717#issuecomment-2269789609)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD7TGQFC4UH7ONDXR4QFE43ZP7I7BAVCNFSM6AAAAABH7TVE5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZG44DSNRQHE> . You are receiving this because you were mentioned.Message ID: ***@***.***> Thanks @trlopes1974 . You have provided a log of useful information on this issue. I was following your logs and trying to understand what exactly happened. This is not a reproducible issue on my side, there needs to be a combination of different things to happen together to lead to this bug. The main component involved could be: Scheduler side: mainly the interaction with executor to check task status and re-queue task: 1. scheduler heartbeat executor to process event: https://github.com/apache/airflow/blame/main/airflow/jobs/scheduler_job_runner.py#L879-L904 2. scheduler timer to fail task which has been queued long enough: https://github.com/apache/airflow/blob/main/airflow/jobs/scheduler_job_runner.py#L1091-L1094 Worker side: I don't notice anything abnormal on the worker side when the scheduler error happens for now yet. -- 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]
