hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16972) Log more details for Scan#next request when responseTooSlow
Date Tue, 01 Nov 2016 05:50:58 GMT

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

stack commented on HBASE-16972:
-------------------------------

One suggestion is that you have the ScanRequest protobuf. Elsewhere in RpcServer we print
out the param. You might do same here. Here is an example output w/ the param printed out.
Doesn't have table name but taht is in the region.  See what you think.


{code}
2016-10-20 13:05:21,302 TRACE org.apache.hadoop.hbase.ipc.RpcServer: callId: 461613696 service:
ClientService methodName: Scan size: 323 connection: 172.17.183.15:54355 param: region { type:
REGIO      N_NAME value: "raw_support_case,5008000000ecQyfAAE\000\000\377\377\377\377\253G\312,1426540404421.2ea42fcd1adf3b64336c38bcd67fed6f."
} scan { column { family: "observable" qualifier: "dirty" } sta      rt_row: "5008000000ecQyfAAE\000\000\377\377\377\377\253G\312"
filter { name: "org.apache.hadoop.hbase.filter.SingleColumnValueFilter" serialized_filter:
"\n\nobservable\022\005dirty\030\002\"8\n/o      rg.apache.hadoop.hbase.filter.BinaryComparator\022\005\n\003\n\001\001(\0010\001"
} max_versions: 1 cache_blocks: true caching: 100 } number_of_rows: 0 close_scanner: false
connection: 172.17.183.      15:54355, response scanner_id: 35453111 more_results: true ttl:
60000 queueTime: 0 processingTime: 1 totalTime: 1
{code}

> Log more details for Scan#next request when responseTooSlow
> -----------------------------------------------------------
>
>                 Key: HBASE-16972
>                 URL: https://issues.apache.org/jira/browse/HBASE-16972
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: Yu Li
>            Assignee: Yu Li
>         Attachments: HBASE-16972.patch
>
>
> Currently for if responseTooSlow happens on the scan.next call, we will get warn log
like below:
> {noformat}
> 2016-10-31 11:43:23,430 WARN  [RpcServer.FifoWFPBQ.priority.handler=5,queue=1,port=60193]
ipc.RpcServer(2574):
> (responseTooSlow): {"call":"Scan(org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ScanRequest)",
> "starttimems":1477885403428,"responsesize":52,"method":"Scan","param":"scanner_id: 11
number_of_rows: 2147483647
> close_scanner: false next_call_seq: 0 client_handles_partials: true client_handles_heartbeats:
true
> track_scan_metrics: false renew: false","processingtimems":2,"client":"127.0.0.1:60254","queuetimems":0,"class":"HMaster"}
> {noformat}
> From which we only have a {{scanner_id}} and impossible to know what exactly this scan
is about, like against which region of which table.
> After this JIRA, we will improve the message to something like below (notice the last
line):
> {noformat}
> 2016-10-31 11:43:23,430 WARN  [RpcServer.FifoWFPBQ.priority.handler=5,queue=1,port=60193]
ipc.RpcServer(2574):
> (responseTooSlow): {"call":"Scan(org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ScanRequest)",
> "starttimems":1477885403428,"responsesize":52,"method":"Scan","param":"scanner_id: 11
number_of_rows: 2147483647
> close_scanner: false next_call_seq: 0 client_handles_partials: true client_handles_heartbeats:
true
> track_scan_metrics: false renew: false","processingtimems":2,"client":"127.0.0.1:60254","queuetimems":0,"class":"HMaster",
> "scandetails":"table: hbase:meta region: hbase:meta,,1.1588230740"}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message