Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21179

Fix the number of actions in responseTooSlow log

    Details

      Description

      responseTooSlow

      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., for 1 actions and 1st row key=\\x00\\x00.[\\x96
      x16p","starttimems":1536566911759,"queuetimems":0,"class":"HRegionServer","responsesize":2,"method":"Multi"}

      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.

        Attachments

        1. HBASE-21179.master.002.patch
          2 kB
          Guangxu Cheng
        2. HBASE-21179.master.001.patch
          2 kB
          Guangxu Cheng
        3. HBASE-21179.branch-1.001.patch
          2 kB
          Guangxu Cheng

          Activity

            People

            • Assignee:
              andrewcheng Guangxu Cheng
              Reporter:
              andrewcheng Guangxu Cheng
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: