hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14041) CLI command to prune old metadata
Date Wed, 08 Feb 2017 18:10:42 GMT

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

Sean Mackrory updated HADOOP-14041:
    Attachment: HADOOP-14041-HADOOP-13345.003.patch

Okay - let's punt on directory pruning for now. Adding mod_time to directories or addressing
the other concerns you've raised would be a big enough deal to be a separate issue, I think.
So I'll file JIRAs to address that if we go with the approach I just attached.

In this patch I remove the directory logic, but add back a test to confirm that directories
are not getting removed yet (with a comment about why we check for that behavior).

I also got a request to make the default age configurable (e.g. in .xml files) so individual
commands don't need to specify it. I think that's a good idea, but I'm not sure if there's
a precedent / established naming convention for that in CLI commands. I think it makes a lot
of sense to do that, especially since if you don't specify things like the metastore table
/ endpoint it does fall back on what's configured. I still have it so you can override with
"-H 12", for instance, on the command-line.

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

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

View raw message