Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 14 Aug 2013 17:46:48 +0000 (UTC)
From: "Ravi Mutyala (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12660150.1374879386259.65956.1376502408589@arcas>
In-Reply-To: <JIRA.12660150.1374879386259@arcas>
References: <JIRA.12660150.1374879386259@arcas>
Subject: [jira] [Commented] (ACCUMULO-1618) No ability to disable trash for
 root tablet & WAL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739940#comment-13739940 ] 

Ravi Mutyala commented on ACCUMULO-1618:
----------------------------------------

True. I was watching that item, and didn't realize there was another jira that went in for serverside trash configuration on v2. So, this patch will fail on 2.0 branch. 

I will go ahead and make a change to fix fs.moveToTrash with the check. I believe loading the configs more than once to not require full system restart should have its own ticket and tracked separately. 
                
> No ability to disable trash for root tablet & WAL
> -------------------------------------------------
>
>                 Key: ACCUMULO-1618
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1618
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.5.0
>            Reporter: John Vines
>             Fix For: 1.5.1, 1.6.0
>
>
> In 1.5 we changed the check in the garbage collector from a flag that gets passed in into a system setting. However, there are a few other places in the code where we want to provide the ability to bypass the trash. At least one is in the Tablet.java#bringMajorCompactionOnline. There is another case in the WALs, but the errors don't have stack traces.

--
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