You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2015/09/18 23:37:05 UTC

[jira] [Resolved] (HBASE-14333) responseTooLarge/Slow logs are not actionable when the rpc method is ExecService

     [ https://issues.apache.org/jira/browse/HBASE-14333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk resolved HBASE-14333.
----------------------------------
    Resolution: Duplicate

Superseded by efforts on HBASE-14443.

> responseTooLarge/Slow logs are not actionable when the rpc method is ExecService
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-14333
>                 URL: https://issues.apache.org/jira/browse/HBASE-14333
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: Nick Dimiduk
>              Labels: beginner
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)