hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16708) Expose endpoint Coprocessor name in "responseTooSlow" log messages
Date Mon, 05 Dec 2016 17:40:58 GMT

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

Hudson commented on HBASE-16708:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-0.98-matrix #422 (See [https://builds.apache.org/job/HBase-0.98-matrix/422/])
HBASE-16708 Expose endpoint Coprocessor name in responseTooSlow log (apurtell: rev 691af41d1046482263fca6f67aa1418f6944858f)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java


> 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.0.0
>            Reporter: Nick Dimiduk
>            Assignee: Yi Liang
>             Fix For: 2.0.0, 1.4.0, 0.98.24
>
>         Attachments: HBASE-16708-Branch1.patch, HBASE-16708-V1.patch, HBASE-16708-V2.patch,
HBASE-16708-V3.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