hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5277) hadoop fs -expunge does not work for federated namespace
Date Mon, 30 Sep 2013 17:55:24 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782046#comment-13782046

Vrushali C commented on HDFS-5277:

Trying to expose federated namespace from within FSShell to get expunge working might be tricky
and not very clean. Passing a filesystem argument to the expunge works and results in creating
a timestamp-named directory inside trash and moves the contents under current to that dir.

For example, if one of the namespaces is called "namespace1" in the cluster, a command like
the following will work:
$hadoop fs -fs hdfs://namespace1/  -expunge
13/09/27 23:07:06 INFO fs.TrashPolicyDefault: Created trash checkpoint: /user/hadoop/.Trash/130927230706
$ hadoop fs -ls hdfs://namespace1/user/hadoop/.Trash
Found 1 items
drwx------ - hadoop hadoop 0 2013-09-27 22:59 hdfs://namespace1/user/hadoop/.Trash/130927230706

> hadoop fs -expunge does not work for federated namespace 
> ---------------------------------------------------------
>                 Key: HDFS-5277
>                 URL: https://issues.apache.org/jira/browse/HDFS-5277
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.5-alpha
>            Reporter: Vrushali C
> We noticed that hadoop fs -expunge command does not work across federated namespace.
This seems to look at only /user/<username>/.Trash instead of traversing all available
namespace and expunging from individual namespace.

This message was sent by Atlassian JIRA

View raw message