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

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

potiuk edited a comment on issue #19192:
URL: https://github.com/apache/airflow/issues/19192#issuecomment-954126509


   It does not look like like Airflow problem to be honest. 
   
   It certainly looks like your long running task blocks some resources that blocks scheduler somehow (but there is no indication how it can be blocked). There must be something in your DAGs or task that simply causes the Airflow scheduler to lock up. 
   
   This is almost certainly something specific to your deployment (others do not experience it). But what it is, it's hard to say from the information provided.
   
   My best guess is that you have some lock  on the database and it makes scheduler wait while running some query. 
   
   Is it possible to dump the state of scheduler and dump generaly more of the state of your machine, resouces, sockets, DB locks while it happens (this shoudl be possible with py-spy for example). Also getting all logs of scheduler and seing if it actually "does" something might help.  Unfortunately the information we have now is not enough to deduce the reason.
   
   Any insight of WHERE the schduler is locked might help with investigating it.


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