Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 4 Jun 2015 18:01:39 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12835099.1433348696000.13768.1433440899159@Atlassian.JIRA>
In-Reply-To: <JIRA.12835099.1433348696000@Atlassian.JIRA>
References: <JIRA.12835099.1433348696000@Atlassian.JIRA>
 <JIRA.12835099.1433348696938@arcas>
Subject: [jira] [Updated] (ACCUMULO-3885) Shouldn't short circuit multiple
 compaction requests if iterators have changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs updated ACCUMULO-3885:
----------------------------------------
    Fix Version/s: 1.8.0

> Shouldn't short circuit multiple compaction requests if iterators have changed
> ------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3885
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3885
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.6.0
>            Reporter: John Vines
>             Fix For: 1.8.0
>
>
> Currently if you force a compaction and then force another one, accumulo has a convenience feature that doesn't force the redundant one. The problem is if you change iterators settings for majc time between compaction calls, the second one is no longer redundant and the feature is now a hindrance. We should compare state of the iterators between the currently running compaction and the current state before decided to drop the second attempt.


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