hbase-issues mailing list archives

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

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

Nick Dimiduk commented on HBASE-16972:
--------------------------------------

Change appears only to add new fields to a json-ish blob, so I'm (belatedly) okay with this
for release lines. It would break folks who are parsing positionally, but it's structured,
so they don't have so much room to complain.

Strong objections [~busbey]? I guess it's already out in 1.2.4, so that's that.

> 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
>    Affects Versions: 1.2.3, 1.1.7
>            Reporter: Yu Li
>            Assignee: Yu Li
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.4, 1.1.8
>
>         Attachments: HBASE-16972.patch, HBASE-16972.v2.patch, HBASE-16972.v3.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