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 22:06:58 GMT

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

Yi Liang commented on HBASE-16708:

Hi [~ndimiduk]
   Carry your comments to show the full class name, since the full class name is only stored
in a map called coprocessorServiceHandlers in region, register each coprocessor, and it is
a map store <ServiceName, Real ServiceClass>. Use my case as example, the coprocessorServiceHandlers
will store <SumService, org.myname.hbase.coprocessor.endpoint.SumEndPoint>, the SumService
is created by xx.proto, and SumEndPoint is the coprocessor class extend SumService. So the
only way to get the full class name  is through coprocessorServiceHandlers.  The detail about
how to get access to coprocessorServiceHandlers is in the patch, could you help me to review
it. Thanks
    The current output looks like: 
2016-11-15 13:34:22,191 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":1479245662059,"responsesize":127,"method":"ExecService","param":"endpoint
coprocessor= class org.myname.hbase.coprocessor.endpoint.SumEndPoint:getSum","processingtimems":131,"client":"","queuetimems":1,"class":"HRegionServer"}

> 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