Uh oh!
There was an error while loading. Please reload this page.
HBASE-23381: Improve Logging in HBase Commons Package - #913
Closed
belugabehr wants to merge 3 commits into
Closed
Conversation
Apache-HBase
commented
Dec 6, 2019
💔 -1 overall
This message was automatically generated. |
HorizonNet
left a comment
Contributor
There was a problem hiding this comment.
LGTM overall, but left a general question.
| if (LOG.isInfoEnabled()) { | ||
| LOG.info("Could not successfully schedule chore: " + chore.getName()); | ||
| } | ||
| LOG.info("Could not successfully schedule chore: " + chore.getName()); |
Contributor
There was a problem hiding this comment.
Why did you remove the check?
Contributor
There was a problem hiding this comment.
Please use parameterized logging for the name. Also probably better to just pass the chore so we get the name and the desired period.
ContributorAuthor
There was a problem hiding this comment.
@HorizonNet The LOG.info method will check internally if the log level is set to Info before emitting a log message, no need to do it twice. Since the log message is INFO level, it's almost certainly going to be enabled when running in production so it's not worth being too clever with regards to performance so I wouldn't normally bother making it parameterized if it's not already. However, I will make that adjustment since I'll emit the chore object instead of its getName().
Also, this should be an ERROR level logging, to include the stack trace.
Contributor
There was a problem hiding this comment.
that's a good catch. This exception handling used to also be used as a non-error condition way of disabling the chore. agree that now it should probably call more attention to itself.
busbey
requested changes
Dec 8, 2019
busbey
left a comment
Contributor
There was a problem hiding this comment.
Some feedback. Still reviewing
| if (LOG.isInfoEnabled()) { | ||
| LOG.info("Could not successfully schedule chore: " + chore.getName()); | ||
| } | ||
| LOG.info("Could not successfully schedule chore: " + chore.getName()); |
Contributor
There was a problem hiding this comment.
Please use parameterized logging for the name. Also probably better to just pass the chore so we get the name and the desired period.
Uh oh!
There was an error while loading. Please reload this page.
| printChoreServiceDetails("requestCorePoolIncrease"); | ||
| if (LOG.isTraceEnabled()) { | ||
| LOG.trace("requestCorePoolIncrease"); |
Contributor
There was a problem hiding this comment.
Why not leave all of this in the method and have it do a proper trace guard?
ContributorAuthor
There was a problem hiding this comment.
Personal taste. It seems overkill to have a method just for logging. Nicer when I can just see the logging and move on with my life, not having to jump into a method. If that logging method was used 10 times and/or this method was heavily overloaded, I'd probably keep it, but for 2x, and some simple methods, it doesn't feel worth it.
ContributorAuthor
There was a problem hiding this comment.
... it also gets confusing because folks need to know who is responsible for the logging guards... internal or external to the method. I've seen it done both ways and I've seen where people then don't include guards when they should or they double-bag it.
Uh oh!
There was an error while loading. Please reload this page.
| @InterfaceAudience.Private | ||
| public class KeyValueUtil { | ||
| private static final Logger LOG = LoggerFactory.getLogger(KeyValueUtil.class); |
Contributor
There was a problem hiding this comment.
I'll have to review where we call these utility methods since we're pulling out all this logging.
Please no one merge this util someone has done that check.
ContributorAuthor
There was a problem hiding this comment.
Great. Thanks. This goes under the heading of 'log and throw'.
Contributor
There was a problem hiding this comment.
that's well and good in principle but only works if we actually log something about the exception when it's eventually caught. also depending on the severity it might be needed if we're at risk of stacktrace optimization by the JVM and log rolling making it so we can't actually get details from here when it comes time to log the exception elsewhere.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Apache-HBase
commented
Dec 11, 2019
💔 -1 overall
This message was automatically generated. |
belugabehr
commented
Dec 12, 2019
ContributorAuthor
@busbey Made the requested changes. Just need your verdict on KeyValueUtil.java log-and-throw |
Apache-HBase
commented
Dec 12, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Dec 12, 2019
💔 -1 overall
This message was automatically generated. |
belugabehr
commented
Dec 12, 2019
ContributorAuthor
Sorry. I got all mixed up in my local repo. I ended up rebasing to squash my three commits and doing a force push. Sorry for the inconvenience. |
Apache-HBase
commented
Dec 13, 2019
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Dec 30, 2019
💔 -1 overall
This message was automatically generated. |
saintstack
commented
Jan 2, 2020
Contributor
@busbey Want to give a blessing here sir? |
belugabehr
commented
Feb 6, 2020
ContributorAuthor
@saintstack@busbey Just merged in latest changes and fixed conflicts. Thanks! |
Apache-HBase
commented
Feb 6, 2020
💔 -1 overall
This message was automatically generated. |
Apache9
commented
Jul 27, 2020
Contributor
Is this one still active? |
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
6 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.
No description provided.