-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-22283 Print row and table information when failed to get region location #181
Conversation
💔 -1 overall
This message was automatically generated. |
Checking
|
🎊 +1 overall
This message was automatically generated. |
pre-commit check looks good, waiting for review, 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.
Patch looks good except for part where we are pre-making error string though we only use it when a problem. Do we have to do this? Can we not just make the error string when an error? Thanks @carp84
Thanks for review @saintstack, have just updated the PR following the suggestion. |
🎊 +1 overall
This message was automatically generated. |
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.
Yeah, it dupes code but this is better I think. Thanks @carp84
Thanks @saintstack, merged into master and manually pushed into branch-1/branch-2 |
What is the purpose of the change
This PR refines the client logging message on
RpcRetryingCallerWithReadReplicas.getRegionLocations
for easier debugging.Brief change log
RpcRetryingCallerWithReadReplicas.getRegionLocations
when failed to get region location or the location got is null.Verifying this change
This change could be verified by existing tests.
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation