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

feat(sandbox): kill child workers gracefully #1802

Conversation

GabrielCastro
Copy link
Contributor

Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Queue.close now also kills the workers and waits for them to close

@GabrielCastro GabrielCastro force-pushed the feat/kill-sandboxed-workers-gracefully branch from e55f0d1 to fc19340 Compare July 15, 2020 19:38
GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 15, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
@GabrielCastro GabrielCastro force-pushed the feat/kill-sandboxed-workers-gracefully branch 4 times, most recently from 01c77f4 to fb4ecb9 Compare July 15, 2020 22:11
@coveralls
Copy link

coveralls commented Jul 15, 2020

Coverage Status

Coverage decreased (-0.2%) to 95.2% when pulling ce35559 on GabrielCastro:feat/kill-sandboxed-workers-gracefully into c23ed74 on OptimalBits:develop.

GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 21, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 21, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 21, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 21, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 21, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
GabrielCastro added a commit to GabrielCastro/bullmq that referenced this pull request Jul 23, 2020
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Worker#close now also kills the workers and waits for them to close

This is the same feature as OptimalBits/bull#1802
Properly handle SIGTERM in the child workers by waiting for the current
job to exit, then exiting cleanly.

Queue.close now also kills the workers and waits for them to close
@GabrielCastro GabrielCastro force-pushed the feat/kill-sandboxed-workers-gracefully branch 2 times, most recently from 1acb258 to bb26001 Compare July 24, 2020 13:20
@GabrielCastro
Copy link
Contributor Author

@manast This is the same change as taskforcesh/bullmq#243 would it be possible to back-port it here too

@manast manast merged commit 332a96b into OptimalBits:develop Jul 24, 2020
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

Successfully merging this pull request may close these issues.

None yet

3 participants