Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep jobs running in a scale-down event #140

Open
benjii opened this issue Sep 7, 2019 · 0 comments
Open

Keep jobs running in a scale-down event #140

benjii opened this issue Sep 7, 2019 · 0 comments

Comments

@benjii
Copy link

benjii commented Sep 7, 2019

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant