MarvinSchenkel edited a comment on issue #17507: URL: https://github.com/apache/airflow/issues/17507#issuecomment-919072710
> Hello @MarvinSchenkel , to increase the scheduler heartbeat signal you can either export it in your env variable when installing airflow or after having already installed it modifiy the param your airflow.cfg file. > > * bash profile: `export AIRFLOW__SCHEDULER__SCHEDULER_HEARTBEAT_SEC=120` > * airflow.cfg: `scheduler_heartbeat_sec=120`. > > to make sure that the values are correctly set you can use > `airflow config get-value scheduler scheduler_heartbeat_sec` btw > > And then restart the scheduler and the webserver. Thanks for your reply. I tried this and it seems to be sorta working. I am not receiving any more SIGTERM errors. However, I constantly receive the message "The scheduler does not seem to be running". If I look at my k8s cluster overview, I can see that the scheduler pod constantly gets restarted because it seems offline. So it feels more like a happy coincidence, rather than a proper fix :-). I also tried settings `AIRFLOW__CORE__KILLED_TASK_CLEANUP_TIME` to `604800` and `AIRFLOW__SCHEDULER__SCHEDULE_AFTER_TASK_EXECUTION` to `False`, but unfortunately, still receiving SIGTERMs. -- 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]
