You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See this comment which discusses exposing the TASK_GRACE_INTERVAL as a setting. This is an RFE requesting that.
I don't know how long a heartbeat is so if the setting is expressed in heartbeats (which I think I'm ok with), then I need to know how long that is.
As a user, it would be nicer to me if it was expressable in seconds. For example we also have k8s hard timeout values and those are expressed in seconds, and we need to set these similarly and together, so having them all on a seconds timescale is nicer for me. It'll be ok though if not.
The text was updated successfully, but these errors were encountered:
Well heartbeat duration is afaik a setting.
But also this grace time is not a precise time interval. It is measured by counting the ticking by of heartbeats. So the actual resulting time depends on where in the rhythm of the heart an event occured.
If we want more precise timing of stuff we need to rewrite the workers using async python.
See this comment which discusses exposing the
TASK_GRACE_INTERVAL
as a setting. This is an RFE requesting that.I don't know how long a heartbeat is so if the setting is expressed in heartbeats (which I think I'm ok with), then I need to know how long that is.
As a user, it would be nicer to me if it was expressable in seconds. For example we also have k8s hard timeout values and those are expressed in seconds, and we need to set these similarly and together, so having them all on a seconds timescale is nicer for me. It'll be ok though if not.
The text was updated successfully, but these errors were encountered: