pdellarciprete commented on issue #57618: URL: https://github.com/apache/airflow/issues/57618#issuecomment-3660014436
IMO, the adoption of an orphaned task should not increment the `try_number`. Additionally, the KubernetesExecutor should verify before creating a new Pod whether the task instance is still assigned to the same `scheduler_job_id`. Is there a way to disable the orphaned task adoption cycle and simply mark the task as failed if one scheduler abandon it (like relying on task heartbeat timeout)? -- 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]
