[
https://issues.apache.org/jira/browse/HADOOP-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707774#action_12707774
]
dhruba borthakur commented on HADOOP-5712:
------------------------------------------
The proposal of using the timestamp instead of a monotonically increasing
number solves the issue. However, it is not very user-friendly. What do other
filesystems that have a Trash feature do in this case... the only other FS that
I know of implements this feature uses the monotonically increasing number
instead of appending the timestamp. At present, it is very easy to find out the
last version of the file in Trash.
Another option would be to make the Trash client retrieve the contents of the
Trash directory and then scan what files pre-exist in the list. Also, this code
is not fool-proof because there is no atomicity between the exists and the
rename.
> Namenode slowed down when many files with same filename were moved to Trash
> ---------------------------------------------------------------------------
>
> Key: HADOOP-5712
> URL: https://issues.apache.org/jira/browse/HADOOP-5712
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.3
> Reporter: Koji Noguchi
> Priority: Minor
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
