hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16708) Expose endpoint Coprocessor name in "responseTooSlow" log messages
Date Tue, 15 Nov 2016 16:59:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667653#comment-15667653

Nick Dimiduk commented on HBASE-16708:

Thanks for picking this up [~easyliangjob]. This is looking better! Maybe it's better to include
the fully qualified classname, i.e., "com.foo.bar.SumService"?

I wonder if we could replace entirely the "ExecService(...CoprocessorServiceRequest)" with
the coprocessor implementation itself.

> Expose endpoint Coprocessor name in "responseTooSlow" log messages
> ------------------------------------------------------------------
>                 Key: HBASE-16708
>                 URL: https://issues.apache.org/jira/browse/HBASE-16708
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 1.1.2
>            Reporter: Nick Dimiduk
>            Assignee: Yi Liang
> Operational diagnostics of a Phoenix install would be easier if we included which endpoint
coprocessor was being called in this responseTooSlow WARN message.

This message was sent by Atlassian JIRA

View raw message