Bowrna commented on issue #31810: URL: https://github.com/apache/airflow/issues/31810#issuecomment-1711174286
> Sorry, I'm a bit unsure if #34160 really closes this completely. It touches suggestion A above, which is good, but i think one or all of B,C,D are also needed. > > In fact i think the change makes the log message even more confusing than before. By saying "_Scheduler is in unhealthy state_", when the error is most of the time caused by **Executor** not having connection to the database, this is going to mislead people into debugging **scheduler**-issues, instead of connectivity issues. I think its important operators can understand and act on log messages, without having intricate knowledge of the airflow internals. > > I may give this a another go myself but quite busy with other things so don't want to promise anything. hi @hterik .. Its an error due to DBAPI error but when the Scheduler health check threshold is beyond the configured time then wouldn't it be right to mark the scheduler is in unhealthy state? Maybe we can phrase it like "DB not reachable to update for long time leading to unhealthy scheduler state". Please share your views on this. cc: @potiuk -- 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]
