You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/02/01 20:12:01 UTC
[jira] [Updated] (HBASE-21047) Object creation of StoreFileScanner
thru constructor and close may leave refCount to -1
[ https://issues.apache.org/jira/browse/HBASE-21047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-21047:
-----------------------------------
Fix Version/s: (was: 1.5.0)
> Object creation of StoreFileScanner thru constructor and close may leave refCount to -1
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-21047
> URL: https://issues.apache.org/jira/browse/HBASE-21047
> Project: HBase
> Issue Type: Bug
> Reporter: Vishal Khandelwal
> Assignee: Vishal Khandelwal
> Priority: Major
> Fix For: 3.0.0, 1.3.3, 2.2.0, 2.1.1, 2.0.2, 1.4.7
>
> Attachments: HBASE-21047.branch-1.v1.patch, HBASE-21047.branch-1.v2.patch, HBASE-21047.v1.patch
>
>
> During object creation "*StoreFileScanner*", it does not increase the refCount whereas while close it decrements the reader refCount. This will cause refCount to -1 and isReadReference method was returning true (refCount.get() != 0 This is causing store file not to be deleted. This may also cause issue in situation when some thread is holding a scanner but it may actually be closed due to above bug. Impact of this would be really high. Attatching patch for the fix which makes sure if reference is held either thru getScanner method or constructor, ref is always updated. Patch also contains a test which validates the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)