[GitHub] [airflow] t4n1o commented on issue #19192: The scheduler does not appear to be running. Last heartbeat was received X minutes ago.

[GitBox <gi...@apache.org>]

t4n1o commented on issue #19192:
URL: https://github.com/apache/airflow/issues/19192#issuecomment-1170331034

   > Well. Increasing resource usage when you do not have enough of them is really good fix. Unfortunately only your deploymenent can monitor and indicate if you lack memory or not, so this was indeed a fix to a deployment issue.
   
   A lot of the answers in this thread are upgrade your python, check your deployment, update your airflow, only you know your deployment and so on. I'm sure my server has plenty unused resources. The only question would be if the config can make airflow self-limit the amount of resources it uses, and the other possibility is the logic of the scheduler loop has some function call that's blocking.
   
   I understand the responses are because development time is valuable. So, would you consider linking me to the part of the code where the schedule loop is and maybe I can help figure out what's blocking? And for the config, I can just revert to the default.


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