[jira] [Resolved] (HBASE-16372) References to previous cell in read path should be avoided

["ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-16372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan resolved HBASE-16372.
--------------------------------------------
    Resolution: Fixed

> References to previous cell in read path should be avoided
> ----------------------------------------------------------
>
>                 Key: HBASE-16372
>                 URL: https://issues.apache.org/jira/browse/HBASE-16372
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Scanners
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16372_1.patch, HBASE-16372_10.patch, HBASE-16372_2.patch, HBASE-16372_3.patch, HBASE-16372_5_withfactory.patch, HBASE-16372_6_withfactory.patch, HBASE-16372_7_withfactory.patch, HBASE-16372_9.patch, HBASE-16372_testcase.patch, HBASE-16372_testcase_1.patch
>
>
> Came as part of review discussion in HBASE-15554. If there are references kept to previous cells in the read path, with the Ref count based eviction mechanism in trunk, then chances are there to evict a block backing the previous cell but the read path still does some operations on that garbage collected previous cell leading to incorrect results.
> Areas to target
> -> Storescanner
> -> Bloom filters (particularly in compaction path)
> Thanks to [~anoop.hbase] to point out this in bloomfilter path. But we found it could be in other areas also.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)