[
https://issues.apache.org/jira/browse/HBASE-25542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281778#comment-17281778
]
Hudson commented on HBASE-25542:
--------------------------------
Results for branch master
[build #206 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/206/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/206/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/206/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/206/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Add client detail to scan name so when lease expires, we have clue on who was
> scanning
> --------------------------------------------------------------------------------------
>
> Key: HBASE-25542
> URL: https://issues.apache.org/jira/browse/HBASE-25542
> Project: HBase
> Issue Type: Improvement
> Components: scan
> Affects Versions: 2.3.2
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.2
>
>
> On a busy cluster, seeing a bunch of this:
> {code}
> regionserver.RSRpcServices: Scanner -5594731657924732088 lease expired on
> region hbase:meta,,1.1588230740
> {code}
> Trying to figure out originator is a little tough; there isn't enough in for
> in the above.
> scanid is a long but scan name is a string.. perhaps add in the client
> ip+port as scan id prefix? Or add the info to the value -- probably better --
> and dump it out when we get one of these expirations?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
