hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen O'Donnell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-16140) Add emptyTrash option to purge trash immediately
Date Fri, 22 Feb 2019 18:39:00 GMT

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

Stephen O'Donnell commented on HADOOP-16140:
--------------------------------------------

I put the version down as 3.3.0 for now and submitted the patch.

> Why not just add an option to -expunge. It exists, has tests, documentation, etc?

I am not sure about this. Expunge doesn't really empty the trash as I explained above, it
kind of does what the NN does internally. So if we added an option, eg expunge -emptyNow,
does that make it more or less confusing? It would be pretty easy to add this to expunge and
have it call the new methods I added if we think that makes sense. I am open to doing it either
way.

Any suggestions on what to call the option? 

expunge -immediately
expunge -emptyTrash
expunge -?

I will have a look at the other two points shortly.

> Add emptyTrash option to purge trash immediately
> ------------------------------------------------
>
>                 Key: HADOOP-16140
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16140
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 3.3.0
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>         Attachments: HDFS-14200.001.patch
>
>
> I have always felt the HDFS trash is missing a simple way to empty the current users
trash immediately. We have "expunge" but in my experience supporting clusters, end users find
this confusing. When most end users run expunge, they really want to empty their trash immediately
and get confused when expunge does not do this.
> This can result in users performing somewhat dangerous "skipTrash" operations on the
trash to free up space. The alternative, which most users will not figure out on their own
is:
> # Run the expunge command once - this will move the current folder to a checkpoint and
remove any old checkpoints older than the retention interval
> # Wait over 1 minute and then run expunge again, overriding fs.trash.interval to 1 minute
using the following command hadoop fs -Dfs.trash.interval=1 -expunge.
> With this Jira I am proposing to add a extra command, "hdfs dfs -emptyTrash" that purges
everything in the logged in users Trash directories immediately.
> How would the community feel about adding this new option? I will upload a patch for
comments.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message