You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Sanjay Radia (JIRA)" <ji...@apache.org> on 2011/05/19 23:18:47 UTC
[jira] [Commented] (HADOOP-7310) Trash location needs to be
revisited
[ https://issues.apache.org/jira/browse/HADOOP-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036475#comment-13036475 ]
Sanjay Radia commented on HADOOP-7310:
--------------------------------------
Trash is located at /user/<userName>/.Trash
Its location needs to be revisted:
# Does not work well with Quotas. For example, /user/joe and /project/xx may have quotas. When files are deleted from /project/xx they move to /user/joe/.Trash which causes problems since the user quota is usually much less than that of project-xx.
# If customer has a special data hdfs cluster where there are no home directories, then one is forced to have home directories on this data cluster just to accommodate Trash; this can be confusing or may be used as a way get around quotas.
# With federation, one is likely to have a NN for user accounts and other NNs for /projects, /data etc. The issues listed for point 2 apply here.
I propose two solutions:
* A. Put trash in /Trash/<userName>; generally no quotas will be configured for /Trash since it is cleaned up periodically. This addresses all the three issues raised above. This solution however breaks compatibility. Note Trash applies ONLY to rm's performed via the shell's -rm command.
* B. The trash location is configured as SS configuration variable.
I prefer solution A, since it is one less configuration variable. Do folks see *real* compatibility problem here?
> Trash location needs to be revisited
> ------------------------------------
>
> Key: HADOOP-7310
> URL: https://issues.apache.org/jira/browse/HADOOP-7310
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Fix For: 0.23.0
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira