HDDS-2658. Insight log level reset does not work #289
Closed
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.
What changes were proposed in this pull request?
Reset log level to INFO in a shutdown hook instead of
finally
block.https://issues.apache.org/jira/browse/HDDS-2658
How was this patch tested?
Tested on compose cluster:
Verified that
ozone insight
shows trace-level log. Stoppedozone insight
on terminal 2 (Ctrl-C). Verified that creating another volume is logged in terminal 1 (ie. OM), but debug/trace-level messages are not:https://github.com/adoroszlai/hadoop-ozone/runs/330882658