[ http://issues.apache.org/jira/browse/HADOOP-432?page=comments#action_12458016 ] Runping Qi commented on HADOOP-432: -----------------------------------
While it is good to keep deleted files in trash when the space is available, we still need to pay attention to the way we handle them. First, if the space becomes tight, old files should be deleted. Second, we may not need to always keep max copies of the blocks of the files in trash. Definitely, we do not need to re-replicate them when they are slightly below the max replications. Third, when the user deletes files, he/she should be able to choose delete them for good (thus not move to trash), although the default should be the opposite. Lastly, the user should be able to delete files in trash and make them disappear. > support undelete, snapshots, or other mechanism to recover lost files > --------------------------------------------------------------------- > > Key: HADOOP-432 > URL: http://issues.apache.org/jira/browse/HADOOP-432 > Project: Hadoop > Issue Type: Improvement > Components: dfs > Reporter: Yoram Arnon > Assigned To: Wendy Chien > Attachments: undelete12.patch, undelete16.patch, undelete17.patch > > > currently, once you delete a file it's gone forever. > most file systems allow some form of recovery of deleted files. > a simple solution would be an 'undelete' command. > a more comprehensive solution would include snapshots, manual and automatic, > with scheduling options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
