Add SIGINFO logging when service is hard killed#278
Merged
josephharrington merged 1 commit intomasterfrom Dec 14, 2015
Merged
Conversation
The functional testing framework sometimes is unable to kill and restart the service gracefully in between tests. This change sends a SIGINFO signal before doing the hard kill. The debug logs triggered by this signal should give us info about what thread is preventing graceful shutdown.
|
Verified that @josephharrington has signed the CLA. Thanks for the pull request! |
|
👍 |
josephharrington
added a commit
that referenced
this pull request
Dec 14, 2015
Add SIGINFO logging when service is hard killed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The functional testing framework sometimes is unable to kill and
restart the service gracefully in between tests. This change sends a
SIGINFO signal before doing the hard kill. The debug logs triggered by
this signal should give us info about what thread is preventing
graceful shutdown.