[
https://issues.apache.org/jira/browse/HBASE-26731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501796#comment-17501796
]
Hudson commented on HBASE-26731:
--------------------------------
Results for branch master
[build #526 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/526/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/526/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/526/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/526/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}
> Metrics for tracking of active scanners
> ---------------------------------------
>
> Key: HBASE-26731
> URL: https://issues.apache.org/jira/browse/HBASE-26731
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Minor
> Labels: patch-available
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3
>
>
> Active scanners take up resources on the RegionServer. This can result in GC
> issues or even OOMs in cases of leaked scanners. It'd be helpful to have
> metrics for tracking scanners. I was thinking of:
> * activeScanners - a gauge, showing the number of active scanners at a point
> in time
> * scannerLeaseExpirations - a counter of lease expirations
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
