hbase-issues mailing list archives

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

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

Yi Liang commented on HBASE-16708:

Hi Nick,
  I am now working on this jira,  and just research the code, and have a patch now, below
is the sample message for responseTooSlow
2016-11-14 17:14:45,264 WARN  [RpcServer.FifoWFPBQ.default.handler=59,queue=5,port=16020]
ipc.RpcServer: (responseTooLarge): {"call":"ExecService(org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$CoprocessorServiceRequest)","starttimems":1479172485155,"responsesize":127,"method":"ExecService","param":"endpoint
coprocessor= SumService:getSum","processingtimems":108,"client":"","queuetimems":0,"class":"HRegionServer"}

It will output "endpoint coprocessor= SumService:getSum", combine both coprocessor class and
method name, is this good?  or you have any other better suggestion?

> 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
> 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