[GitHub] [airflow] potiuk commented on pull request #28128: Add retry to the scheduler loop to protect against DB hiccups

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk commented on PR #28128:
URL: https://github.com/apache/airflow/pull/28128#issuecomment-1444477621

   > Why was this pull request abandoned? Is there some other method of handling some db hiccups?
   
   because the author abandoned it. If you wish to pick-up after and continue to do so - feel free. 
   
   Best is not to have hiccups (i.e. improving stability of your DB). The assumption of Airlfow is that DB is generally stable. Recovering from "any" DB hiccup is not easy and investing into it is not a goal for Airlfow community in genera. Airflow is not 99.999% available systtem (having robust system like that is a significant investment and few order of magnitude more complexity). Occasionally failing and restarting components where such hiccups do happen is also a viable approach (and this is one that Airflow supports). Generally when any airflow component fails, you should restart it and it should recover. Assumption is that those kind of problems happen rather rarely - this is the **right** approach for your deployment.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org