rwitzel opened a new pull request #11887: URL: https://github.com/apache/airflow/pull/11887
Why? If the Airflow scheduler is restarted (e.g. due to rollout of a new Kubernetes version), then the timeout behaviour of a sensor should not be affected. But before the code change, the timer would start from zero again when the sensor is retried. This was unexpected. Solution: When a sensor is retried, then the sensor uses the start date of the earliest try to justify a time-out. To stay backwards-compatible, the new behaviour is only active when explicitly activated for that sensor. Note: The exponential backoff feature for poking still uses the start date of the current try. This is to keep the code change small. No issues expected from that. related: #9232 (the linked issue cares about execution_timeout for tasks in general, not only sensors) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
