Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 Feb 2017 02:19:41 +0000 (UTC)
From: "Aaron Fabbri (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13039011.1485813443000.93616.1487211581879@Atlassian.JIRA>
In-Reply-To: <JIRA.13039011.1485813443000@Atlassian.JIRA>
References: <JIRA.13039011.1485813443000@Atlassian.JIRA> <JIRA.13039011.1485813443321@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-14041) CLI command to prune old metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Feb 2017 02:19:55 -0000


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

Aaron Fabbri commented on HADOOP-14041:
---------------------------------------

Your latest patch looks good to me, +1.

I'm fine with the default sleep value.  It is at least tunable now, which is great.  Some folks may want it to go fast, others will want to minimize impact to DDB provisioned IO for other live workloads.

Yetus looks clean except for TestKDiag stuff which I believe is unrelated (HADOOP-14030).

I will do some testing and commit this if all looks good.


> CLI command to prune old metadata
> ---------------------------------
>
>                 Key: HADOOP-14041
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14041
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>         Attachments: HADOOP-14041-HADOOP-13345.001.patch, HADOOP-14041-HADOOP-13345.002.patch, HADOOP-14041-HADOOP-13345.003.patch, HADOOP-14041-HADOOP-13345.004.patch, HADOOP-14041-HADOOP-13345.005.patch
>
>
> Add a CLI command that allows users to specify an age at which to prune metadata that hasn't been modified for an extended period of time. Since the primary use-case targeted at the moment is list consistency, it would make sense (especially when authoritative=false) to prune metadata that is expected to have become consistent a long time ago.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org