hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16708) Expose endpoint Coprocessor name in "responseTooSlow" log messages
Date Fri, 18 Nov 2016 02:28:58 GMT

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

Jerry He commented on HBASE-16708:
----------------------------------

I think the short service name looks ok, if we don't have to pull in all the extras into RpcServer.
The service name to the implementation mapping is 1-to-1.  We would loss much clarity.

nit. 
bq. "coprocessor="
Maybe "coprocessorService="?

> 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: 2.0.0
>            Reporter: Nick Dimiduk
>            Assignee: Yi Liang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16708-V1.patch, HBASE-16708-V2.patch, HBASE-ShortName.patch
>
>
> 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
(v6.3.4#6332)

Mime
View raw message