Uh oh!
There was an error while loading. Please reload this page.
HBASE-22283 Print row and table information when failed to get region location - #181
Conversation
Apache-HBase
commented
Apr 22, 2019
💔 -1 overall
This message was automatically generated. |
carp84
commented
Apr 22, 2019
Checking |
Apache-HBase
commented
Apr 22, 2019
🎊 +1 overall
This message was automatically generated. |
carp84
commented
Apr 22, 2019
pre-commit check looks good, waiting for review, thanks. |
saintstack
left a comment
There was a problem hiding this comment.
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
carp84
commented
Apr 23, 2019
Thanks for review @saintstack, have just updated the PR following the suggestion. |
Apache-HBase
commented
Apr 23, 2019
🎊 +1 overall
This message was automatically generated. |
saintstack
left a comment
There was a problem hiding this comment.
Yeah, it dupes code but this is better I think. Thanks @carp84
carp84
commented
Apr 24, 2019
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.getRegionLocationsfor easier debugging.Brief change log
RpcRetryingCallerWithReadReplicas.getRegionLocationswhen 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