[
https://issues.apache.org/jira/browse/HBASE-23349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369296#comment-17369296
]
Viraj Jasani commented on HBASE-23349:
--------------------------------------
{quote} the issue already fixed in 1.7.0 released on 2021/06/12? It is still
marked as UNRESOLVED.
{quote}
This Jira is not yet resolved. Any Jira that is resolved is always marked
"Resolved" with fix versions that indicate which HBase releases the Jira
fix/improvement has landed on.
[~larry1285] how long have you been facing this issue? Are you getting this log
for same HFile for long time or for different HFiles? Are you using any custom
coprocs that might be leaking refCounts? Which HBase version are you using?
> Low refCount preventing archival of compacted away files
> --------------------------------------------------------
>
> Key: HBASE-23349
> URL: https://issues.apache.org/jira/browse/HBASE-23349
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha-1, 2.3.0, 1.6.0
> Reporter: Viraj Jasani
> Priority: Major
>
> We have observed that refCount on compacted away store files as low as 1 is
> prevent archival.
> {code:java}
> regionserver.HStore - Can't archive compacted file
> hdfs://{{root-dir}}/hbase/data/default/t1/12a9e1112e0371955b3db8d3ebb2d298/cf1/73b72f5ddfce4a34a9e01afe7b83c1f9
> because of either isCompactedAway=true or file has reference,
> isReferencedInReads=true, refCount=1, skipping for now.
> {code}
> We should come up with core code (run as part of discharger thread)
> gracefully resolve reader lock issue by resetting ongoing scanners to start
> pointing to new store files instead of compacted away store files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
