ecerulm commented on issue #21087: URL: https://github.com/apache/airflow/issues/21087#issuecomment-1122403109
@snjypl Like I said before, my only concern is that someone that reads this thread maybe get the false impression that watch bookmarks are needed to stop the scheduler from getting stuck in an infinite loop and some people may even get the idea that we need a new kubernets python client before we can solve this, which is not the case. I just tried to explain that watch bookmarks are not needed to solve the infinite loop (which is what this #21087 is about IMHO) . And that watch bookmarks alone will not prevent the 410 at least the scenario that I'm personally experiencing (which I already explained). > i am just trying to help understand the root cause of 410 and possible ways prevent it from recurring. One of the root causes would be the one that I explained, which I don't think can't be prevented from recurring. > both parts are equally important. well, I think a) is more important and that's why I'm so adamant into making sure that a) is done and not delayed waiting for kubernetes client updates, etc. Since just `b) ...reduce the frequency of the error.` does not make a big difference, if my scheduler gets into infinite loop every hour or every day it does not matter that much. Both cases are unacceptable for me. I totally agree to leave it here, I think with these two last post is clear what you mean, and what I mean. -- 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]
