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

Kill unresponsive workers #70

Open
asilvas opened this issue Apr 16, 2015 · 1 comment
Open

Kill unresponsive workers #70

asilvas opened this issue Apr 16, 2015 · 1 comment
Labels
enhancement Hacktoberfest low priority

Comments

@asilvas
Copy link
Collaborator

asilvas commented Apr 16, 2015

A recent situation came up (related to very complex regular expressions) that resulted in the worker hanging. Scenarios like this cannot be auto-fixed by the worker/app itself, as the event loop is dead in the water. No other processing will take place when this happens.

This would be a great addition to cservice, periodic heartbeats. If no response after X seconds, force terminate (and restart) the worker process.
@asilvas
Copy link
Collaborator Author

asilvas commented Apr 16, 2015

Better yet, instead of a pulling, enable auto pushing of heartbeats from the worker. Anyone that doesn't report back within the threshold will be killed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Hacktoberfest low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@asilvas @rxmarbles