Uh oh!
There was an error while loading. Please reload this page.
[HBASE-22592] : HMaster Construction failure stacktrace to be availab… - #311
Closed
virajjasani wants to merge 4 commits into
Closed
[HBASE-22592] : HMaster Construction failure stacktrace to be availab…#311virajjasani wants to merge 4 commits into
virajjasani wants to merge 4 commits into
Conversation
…le in .out file - Useful if Logger class is not loaded yet
This was referenced Jun 16, 2019
Apache-HBase
commented
Jun 16, 2019
💔 -1 overall
This message was automatically generated. |
virajjasani
commented
Jun 16, 2019
ContributorAuthor
retest this please |
HorizonNet
commented
Jun 16, 2019
Contributor
I kicked off another build in case the test failure is unrelated. |
| throw new RuntimeException("HMaster Aborted"); | ||
| } | ||
| } catch (Throwable t) { | ||
| t.printStackTrace(); |
Contributor
There was a problem hiding this comment.
Will the error be present in the log files with this change? Is there a better way to do this, but still using the logger?
ContributorAuthor
There was a problem hiding this comment.
I thought about that but as per the screenshot provided in the description, the Exception provided is not available in log file because Logger is not yet loaded.
Anyways, adding printstacktrace() would ensure that the StackTrace is atleast available in .out file. If the Logger is created and loaded by that time, then it would also be present in .log file based on: LOG.error("Master exiting", t);
Apache-HBase
commented
Jun 16, 2019
💔 -1 overall
This message was automatically generated. |
virajjasani
commented
Jun 17, 2019
ContributorAuthor
Error not relevant. |
Apache-HBase
commented
Jun 17, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 17, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jun 17, 2019
🎊 +1 overall
This message was automatically generated. |
virajjasani
commented
Jun 19, 2019
ContributorAuthor
@apurtell please review |
busbey
requested changes
Jun 19, 2019
busbey
left a comment
Contributor
There was a problem hiding this comment.
we don't print stuff to stdout if there's a logger available. Please refactor to only print if the logging system isn't present. (which I'm not sure is possible)
virajjasani
commented
Jun 19, 2019
ContributorAuthor
@busbey I agree we shouldn't print everything to stdout when logger is available. However, the error present in the screenshot was encountered due to a library that contained some incompatible guava method and HBase had classpath setup to use that library. Hence, when HMaster was started, no error was printed to .log or .out file. We had to attach JDB to figure out this Exception. |
busbey
commented
Jun 19, 2019
Contributor
the current patch prints a stack trace to stdout for any throwable. we know there are lots of ways to bring down the master with a throwable that will have a logger in place. Don't print those to stdout. at a minimum you should be adding a catch block for things that are likely to go wrong in a way that can predate a logger being available in the runtime. The stacktrace in your screen shot shows a problem that should not be possible before the logging system is available (it happens in a catch block in an instance method and the logger is a final static variable that should be initialized already before any instances can be created). So please include a reproduction that ensures proper logging configs. |
virajjasani
commented
Jun 19, 2019
ContributorAuthor
After updating the dependent library, I am not able to repro this Exception anymore. Tried certain ways but didn't get much progress. |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
…le in .out file - Useful if Logger class is not loaded yet
An example of Exception(NoSuchMethodError) which is not present in .log/.out files: