ecerulm commented on PR #23521: URL: https://github.com/apache/airflow/pull/23521#issuecomment-1127719478
Yes, you potentially miss old event just like before. The only difference is that the scheduler does not get into an infinite loop because of it. If airflow gets a 410 from kubernetes api that already is a pretty good indicator that some event has been lost but there is nothing airflow can do about it at that point, right? the question remains if kubernetes offers the right API with the right guarantees to implement this kind of scheduling reliably. Or if other approach would be better. This PR was only about preventing the scheduler from entering an infinite loop in which progress was impossible. -- 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]
