MarvinSchenkel edited a comment on issue #17507:
URL: https://github.com/apache/airflow/issues/17507#issuecomment-919100675


   > On my side I also receive this message that seems correct if the heartbeat 
is X the message should be
   > 
   > ```
   > The scheduler does not appear to be running. Last heartbeat was received X 
/ 60 minutes ago.
   > 
   > The DAGs list may not update, and new tasks will not be scheduled.
   > ```
   > 
   > Also as I said above that is NOT a proper fix
   > "
   > increase the heartbeat signal (so that the tasks gets not killed by the 
heart beat concurrency (mainly for sensors): and will incorporate 
https://github.com/apache/airflow/pull/16289/files in order to fix the race 
condition tomorrow." => that is the proper fix but since it was not available 
in 2.0.2 I have to modify my source code with the commit changes.
   
   Fair enough, so with the fix applied we wouldn't need to set any additional 
configs (like scheduler_heartbeat, killed_task_cleanup_time and 
schedule_task_after_task_execution)? Is there any way to check when this PR is 
going to be released? The PR mentions 2.1.3, but I am still running into these 
issues using 2.1.3.


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


Reply via email to