Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 15 Apr 2015 06:14:59 +0000 (UTC)
From: "jeongmin kim (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12821063.1429078472000.4948.1429078499018@Atlassian.JIRA>
In-Reply-To: <JIRA.12821063.1429078472000@Atlassian.JIRA>
References: <JIRA.12821063.1429078472000@Atlassian.JIRA>
 <JIRA.12821063.1429078472849@arcas>
Subject: [jira] [Created] (HBASE-13473) deleted cells come back alive after
 the stripe compaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

jeongmin kim created HBASE-13473:
------------------------------------

             Summary: deleted cells come back alive after the stripe compaction
                 Key: HBASE-13473
                 URL: https://issues.apache.org/jira/browse/HBASE-13473
             Project: HBase
          Issue Type: Bug
          Components: Compaction
    Affects Versions: 0.98.12, 2.0.0, 1.0.1, 1.1.0
            Reporter: jeongmin kim
            Priority: Blocker
             Fix For: 2.0.0, 1.1.1, 0.98.13


during the STRIPE compaction,
deletes(tombstones) are being dropped in 2 cases.
1. Compaction including L0  (includeL0 == true)
2. L0 has no files (canDropDeletesWithoutL0 == true)

To drop delete marker and keep the consistency during compaction, 
All of HFiles in the stripe has to be selected, just like major compaction.
otherwise, after the compaction only delete markers would be gone, 
and deleted cells (which is in the not-selected HFiles) are going to be alive again.
In my cluster, there was no file on L0 and not all file selected for compaction, so some of delete rows have come back alive after delete.

I made a patch about it.
it checks if all files are selected before we set the majorRange of compaction request .


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