-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-24182 log when the region is set to closing status #1509
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
Conversation
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
virajjasani
left a comment
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.
We are already logging close region journal as per HBASE-22828. No need to have additional info log.
|
@virajjasani No strong opinion from me but the one new INFO level log inline with other logging seems fine. The close journal is printed after the fact and so is a bit confusing if you are sorting log lines chronologically. Sure, overall the logging is redundant. |
Sure, for the sake of chronological sorting, it is good to log this. Let's get it. |
| } | ||
| } | ||
| this.closing.set(true); | ||
| LOG.info("Closing {}", this); |
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.
@Joseph295 Can you change this to "Closing region {}"? this is anyways going to print region name as string only.
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.
@Joseph295 Can you change this to "Closing region {}"?
thisis anyways going to print region name as string only.
I think the discussion above really makes sense, so do you guys think we add this log any more? maybe for debug level is enough? We only need it if we concern about the closing cost time for debug? Anyway, let me fix the format for that, any suggestion is welcome. Thanks
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.
Journal log is at Debug level anyways right? Let this be Info level, should be good. Imp point here is of timing of these logs and hence, if we debug from logs based on region name, we can see sorting of chronological events one after another and that way having this Info log is beneficial (although redundant).
Let's wait for @apurtell 's final call on this.
virajjasani
left a comment
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.
Updating my vote to +1
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
Signed-off-by: stack <[email protected]>
Signed-off-by: stack <[email protected]>
Signed-off-by: stack <[email protected]>
Signed-off-by: stack <[email protected]>
No description provided.