[jira] [Commented] (HBASE-25542) Add client detail to scan name so when lease expires, we have clue on who was scanning

2021-02-09 Thread Hudson (Jira) 


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

Hudson commented on HBASE-25542:


Results for branch branch-2.4
[build #48 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/48/]:
 (/) *{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/branch-2.4/48/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/48/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {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/branch-2.4/48/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/branch-2.4/48/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)

[jira] [Commented] (HBASE-25542) Add client detail to scan name so when lease expires, we have clue on who was scanning

2021-02-09 Thread Hudson (Jira) 


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

Hudson commented on HBASE-25542:


Results for branch branch-2
[build #173 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/173/]:
 (/) *{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/branch-2/173/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/173/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {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/branch-2/173/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/branch-2/173/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)

[jira] [Commented] (HBASE-25542) Add client detail to scan name so when lease expires, we have clue on who was scanning

2021-02-09 Thread Hudson (Jira) 


[ 
https://issues.apache.org/jira/browse/HBASE-25542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (HBASE-25542) Add client detail to scan name so when lease expires, we have clue on who was scanning

2021-02-02 Thread Michael Stack (Jira) 


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

Michael Stack commented on HBASE-25542:
---

bq.  Just record the client name in the RegionScannerHolder and log it out?

That sounds right [~zhangduo] (I tried to say similar with " Or add the info to 
the value – probably better – and dump it out when we get one of these 
expirations?...")

> 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
>Priority: Major
>
> 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)

[jira] [Commented] (HBASE-25542) Add client detail to scan name so when lease expires, we have clue on who was scanning

2021-02-01 Thread Duo Zhang (Jira) 


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

Duo Zhang commented on HBASE-25542:
---

I think when logging this line, we have a RegionScannerHolder at region server 
side? Just record the client name in the RegionScannerHolder and log it out?

> 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
>Priority: Major
>
> 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)