[
https://issues.apache.org/jira/browse/HBASE-23349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984754#comment-16984754
]
Viraj Jasani commented on HBASE-23349:
--------------------------------------
For now, just want to expose the metric and not thinking of reopening the
region since very low counts e.g. 1 or 2 might not be justifiable for region
reopen. Probably we can have time duration based check or better recovery built
on this but still better to expose the refCount per region.
At least based on this metric, manual action can be taken at client or
coprocessor or server side before it is too late.
> Expose max refCount among all compacted store files of a region
> ---------------------------------------------------------------
>
> Key: HBASE-23349
> URL: https://issues.apache.org/jira/browse/HBASE-23349
> Project: HBase
> Issue Type: Task
> Affects Versions: 3.0.0, 2.3.0, 1.6.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> We should expose a region level metric that represents max refCount among
> refCounts of all compacted store files under the region. For successful
> archival of compacted store files, it is important for this metric count to
> be 0 eventually if not immediately. If it is >0 for a considerably high
> amount of time, it indicates some issue i.e. reader refCount leak on some
> compacted store files and in such case, archival would not be successful.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
