You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/02/01 20:13:00 UTC

[jira] [Updated] (HBASE-21179) Fix the number of actions in responseTooSlow log

     [ https://issues.apache.org/jira/browse/HBASE-21179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-21179:
-----------------------------------
    Fix Version/s:     (was: 1.5.0)

> Fix the number of actions in responseTooSlow log
> ------------------------------------------------
>
>                 Key: HBASE-21179
>                 URL: https://issues.apache.org/jira/browse/HBASE-21179
>             Project: HBase
>          Issue Type: Bug
>          Components: logging, rpc
>            Reporter: Guangxu Cheng
>            Assignee: Guangxu Cheng
>            Priority: Major
>             Fix For: 3.0.0, 1.3.3, 1.2.8, 2.2.0, 1.4.8, 2.1.1, 2.0.3
>
>         Attachments: HBASE-21179.branch-1.001.patch, HBASE-21179.master.001.patch, HBASE-21179.master.002.patch
>
>
> {panel:title=responseTooSlow|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
> 2018-09-10 16:13:53,022 WARN  [B.DefaultRpcServer.handler=209,queue=29,port=60020] ipc.RpcServer: (responseTooSlow): {"processingtimems":321262,"call":"Multi(org.apache.hadoop.hbase.protobuf.generated.ClientProtos$MultiRequest)","client":"127.0.0.1:56149","param":"region= tsdb,\\x00\\x00.[\\x89\\x1F\\xB0\\x00\\x00\\x01\\x00\\x01Y\\x00\\x00\\x02\\x00\\x00\\x04,1536133210446.7c752de470bd5558a001117b123a5db5., {color:red}for 1 actions and 1st row{color} key=\\x00\\x00.[\\x96\\x16p","starttimems":1536566911759,"queuetimems":0,"class":"HRegionServer","responsesize":2,"method":"Multi"}
> {panel}
> The responseTooSlow log is printed when the processing time of a request exceeds the specified threshold. The number of actions and the contents of the first rowkey in the request will be included in the log.
> However, the number of actions is inaccurate, and it is actually the number of regions that the request needs to visit.
> Just like the logs above, users may be mistaken for using 321262ms to process an action, which is incredible, so we need to fix it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)