Re: [I] Scheduler uses [scheduler]job_heartbeat_sec property for heartbeats instead of [scheduler]scheduler_heartbeat_sec [airflow]

[via GitHub]

potiuk commented on issue #37971:
URL: https://github.com/apache/airflow/issues/37971#issuecomment-1985539571

   The 2.6.3 version  is:
   
   ```
       def is_alive(self, grace_multiplier=2.1):
           """
           Is this job currently alive.
   
           We define alive as in a state of RUNNING, and having sent a heartbeat
           within a multiple of the heartrate (default of 2.1)
   
           :param grace_multiplier: multiplier of heartrate to require heart 
beat
               within
           """
           if self.job_type == "SchedulerJob":
               health_check_threshold: int = conf.getint("scheduler", 
"scheduler_health_check_threshold")
           else:
               health_check_threshold: int = self.heartrate * grace_multiplier
           return (
               self.state == State.RUNNING
               and (timezone.utcnow() - self.latest_heartbeat).total_seconds() 
< health_check_threshold
           )
   ```
   
   So almost for sure it wouldn't have caused the problem.
   
   (BTW. I am trying to see if we can add the fix to 2.8.3 that we vote on 
currently - because otherwise it would affect the whole 2.8 line)


-- 
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-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org