[
https://issues.apache.org/jira/browse/HBASE-26731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-26731:
--------------------------------------
Description:
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 three:
* activeScanners - a gauge, showing the number of active scanners at a point
in time
* scannerLeaseExpirations - a counter of lease expirations
was:
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 three:
* activeScanners - a gauge, showing the number of active scanners at a point
in time
* scannerLeaseExpirations - a counter of lease expirations
The first one would be incremented and decremented as scanners are opened and
closed. The last two would be integrated into the LeaseManager's run loop.
> 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
>
> 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 three:
> * 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)
