I'd open an issue with the full stack trace. There should be exception handling wrapping the scheduler loop so I'm curious to see which part isn't handled properly.
In the meantime I would highly recommend using something like `runit` to restart the process if it exits for some reason. The fact that most people use these supervisor wrapper is probably the reason it never got detected or addressed. Max On Thu, Jun 28, 2018 at 11:02 PM ramandu...@gmail.com <ramandu...@gmail.com> wrote: > Hi All, > We are using airflow 1.9 and are observing scheduler crashes due to mysql > connectivity related issues. > like > "scheduler is crashed because of OperationalError: > (_mysql_exceptions.OperationalError) (2013, 'Lost connection to MySQL > server during query') (Background on this error at: > http://sqlalche.me/e/e3q8)" > Is there a way or config settings to make scheduler more resilient to > Mysql errors. > > Thanks, > Raman Gupta >
