[
https://issues.apache.org/jira/browse/HADOOP-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635438#action_12635438
]
Koji Noguchi commented on HADOOP-4300:
--------------------------------------
I haven't tested on 0.19, but we've been using the Trash feature on our
clusters for some time .
Could you check if Namenode config also has the non-zero fs.trash.interval?
- Client uses 'fs.trash.interval' to determine whether to delete files or move
them to Trash.
- Namenode uses 'fs.trash.interval' for running the expunge thread to clean up
the users' Trash directories.
So your files should be deleted between namenode's 'fs.trash.interval to
'fs.trash.interval * 2' period.
> When fs.trash.interval is set to non-zero value, the deleted files and
> directory which are in .Trash are not getting removed from there after
> <fs.trash.interval>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4300
> URL: https://issues.apache.org/jira/browse/HADOOP-4300
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Ramya R
> Priority: Minor
> Fix For: 0.19.0
>
>
> Set fs.trash.interval to non zero value(say 1), touch a file (say file.txt)
> and delete it. The expected behavior would be that file.txt is moved to
> .Trash and also file.txt is removed from .Trash after 1min. But the observed
> behavior is that, even though file.txt is being moved to .Trash, it is not
> removed from .Trash after 1min.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
