Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C39910FCA for ; Tue, 24 Sep 2013 18:08:10 +0000 (UTC) Received: (qmail 89242 invoked by uid 500); 24 Sep 2013 18:08:08 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 88593 invoked by uid 500); 24 Sep 2013 18:08:05 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 88534 invoked by uid 99); 24 Sep 2013 18:08:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Sep 2013 18:08:02 +0000 Date: Tue, 24 Sep 2013 18:08:02 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-9648) collection one expired storefile causes it to be replaced by another expired storefile MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sergey Shelukhin created HBASE-9648: --------------------------------------- Summary: collection one expired storefile causes it to be replaced by another expired storefile Key: HBASE-9648 URL: https://issues.apache.org/jira/browse/HBASE-9648 Project: HBase Issue Type: Bug Components: Compaction Reporter: Sergey Shelukhin There's a shortcut in compaction selection that causes the selection of expired store files to quickly delete. However, there's also the code that ensures we write at least one file to preserve seqnum. This new empty file is "expired", because it has no data, presumably. So it's collected again, etc. This affects 94, probably also 96. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira