-
Notifications
You must be signed in to change notification settings - Fork 21
CNDB-8830: explicitly log received signal #1950
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
base: main
Are you sure you want to change the base?
Conversation
Checklist before you submit for review
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we've lost the previous build results - push a commit or manually trigger the build again?
assert !isShutdown; | ||
isShutdown = true; | ||
|
||
logger.info("Running data daemon shutdown hook"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be something like "Running StorageService shutdown hook"?
drain(false); | ||
} | ||
|
||
protected synchronized void drain(boolean isFinalShutdown) throws IOException, InterruptedException, ExecutionException |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that if isFinalShutdown == true
some messages are not logged - I wonder if it would be useful to have those logged in the context of CNDB given the ask in the ticket for more logging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are calling setMode though, which happens to optionally log. We could change those to not log and explicitly log instead, wdyt?
What is the issue
To ease service shutdown investigations we could log a received signal.
What does this PR fix and why was it fixed
Logs signals received.