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.

Sign up for GitHub

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

Jump to bottom

Job not labeled as failed when a worker crashes #253

Closed
kstaken opened this issue Jun 23, 2016 · 1 comment
Closed

Job not labeled as failed when a worker crashes #253

kstaken opened this issue Jun 23, 2016 · 1 comment
Labels
priority:high

Comments

@kstaken
Copy link
Member

kstaken commented Jun 23, 2016

If a worker crashes and the slice does not complete the job should be labeled as failed but currently is not.
@kstaken
Copy link
Member Author

kstaken commented Aug 23, 2017

On persistent jobs we've been seeing workers crash with out of memory errors and losing the workers. The job just continues in a running state but down workers.

@godber godber closed this as completed in 8d7fa28 Sep 7, 2017
godber added a commit that referenced this issue Sep 7, 2017
@godber
Merge pull request #525 from jsnoble/job_state_on_worker_crash
7f96c07 
if all workers disconnect, slicer will terminate resolves #253
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:high
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kstaken