Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
This seems to come up mostly for users running Phoenix. We get logs saying a response is too large or slow, but the coprocessoring being invoked is masked. This makes it hard to diagnose which aspect of the query needs to be optimized. Adding the coprocessor class and method would make these log lines much more informative.
Attachments
Issue Links
- is superceded by
-
HBASE-14443 Add request parameter to the TooSlow/TooLarge warn message of RpcServer
- Closed