[
https://issues.apache.org/jira/browse/HBASE-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631891#comment-15631891
]
Mikhail Antonov commented on HBASE-16972:
-----------------------------------------
[~carp84] I totally share and support the aspiration to upgrade to latest and
greatest bits as soon as they come out! :) Really glad to see people waiting
eagerly on 1.3 to be out, hoping to see lots of early adopters benefiting from
it.
But to pave the path for early adoption, we just need to do the best to ensure
that once 1.3 is out it's as production ready as possible, and the actual bits
need to be well baked in. And since new great patches come in every week , at
some point we have to draw the line in the sand and temporarily stop accepting
it - to ship. Once it's there, I'll start reviewing candidate patches for
1.3.1, and this list already includes some good stuff.
Meanwhile, in this window, I see 2 options for potential candidates to 1.3.1 -
either keep the jira open until 1.3.0 is out, or close it and file a backport
jira. For anything less than trivial the latter may be the way to go. What do
you think [~carp84]?
> 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, 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)
