-
Couldn't load subscription status.
- Fork 3.4k
HBASE-26479: Print too slow/big scan's operation_id in region server log #3870
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. |
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.
Mind adding a simple UT for this?
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
Show resolved
Hide resolved
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
…og (#3870) Signed-off-by: Duo Zhang <[email protected]>
…og (#3870) Signed-off-by: Duo Zhang <[email protected]>
Tracing is very important in large-scale distributed systems.
The attribute
_operation.attributes.idof a scan request can be used as trace id between hbase client and region server.We should print operation id in region server's log if the scan request is too slow or too big.
It will be very helpful for finding problematic requests.