Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 8 Aug 2016 08:40:20 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12995578.1470645617000.247065.1470645620699@Atlassian.JIRA>
In-Reply-To: <JIRA.12995578.1470645617000@Atlassian.JIRA>
References: <JIRA.12995578.1470645617000@Atlassian.JIRA> <JIRA.12995578.1470645617216@arcas>
Subject: [jira] [Created] (HBASE-16372) References to previous cell in read
 path should be avoided
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 08 Aug 2016 08:40:22 -0000

ramkrishna.s.vasudevan created HBASE-16372:
----------------------------------------------

             Summary: 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: Bug
          Components: Scanners
    Affects Versions: 2.0.0
            Reporter: ramkrishna.s.vasudevan
            Assignee: ramkrishna.s.vasudevan
            Priority: Critical


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)