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
This is more of a "how is this designed?" rather than an issue (although it might be). I notice that in a scale-down event (i.e.: a node dropping out of a cluster and not being replaced), any jobs running on the removed node are not then run my any other worker in the cluster.
Is this how things are intended?
I originally thought that all workers attempt to run all jobs on all nodes (and it is the cronHistory that constrains the job to only one worker). But this does not seem to be the case. Am I missing something?
The text was updated successfully, but these errors were encountered:
This is more of a "how is this designed?" rather than an issue (although it might be). I notice that in a scale-down event (i.e.: a node dropping out of a cluster and not being replaced), any jobs running on the removed node are not then run my any other worker in the cluster.
Is this how things are intended?
I originally thought that all workers attempt to run all jobs on all nodes (and it is the
cronHistory
that constrains the job to only one worker). But this does not seem to be the case. Am I missing something?The text was updated successfully, but these errors were encountered: