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

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

apilaskowski commented on PR #29815:
URL: https://github.com/apache/airflow/pull/29815#issuecomment-1453217790

   If connection with db is broken then those changes to the db (at this point) would also take place, right?
   Is there some rollback that I missed?
   Is it possible that there is some non-"broken connection" related problem, which could be negatively influenced by those changes?
   
   For us it is critical that expensive job does not get completely restarted, when it does not need to (due to some minor db hiccup).


-- 
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