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 "Harsh J (JIRA)" <ji...@apache.org> on 2015/08/25 07:53:45 UTC
[jira] [Updated] (HADOOP-12352) Delay in checkpointing Trash can
leave trash for 2 intervals before deleting
[ https://issues.apache.org/jira/browse/HADOOP-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-12352:
-----------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
Target Version/s: (was: 2.8.0, 3.0.0)
Status: Resolved (was: Patch Available)
Committed to branch-2 and trunk. Thank you for the find and fix Casey! Hope to see many more.
> Delay in checkpointing Trash can leave trash for 2 intervals before deleting
> ----------------------------------------------------------------------------
>
> Key: HADOOP-12352
> URL: https://issues.apache.org/jira/browse/HADOOP-12352
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Casey Brotherton
> Assignee: Casey Brotherton
> Priority: Trivial
> Fix For: 2.8.0
>
> Attachments: HDFS-8118.001.patch, HDFS-8118.patch
>
>
> When the fs.trash.checkpoint.interval and the fs.trash.interval are set non-zero and the same, it is possible for trash to be left for two intervals.
> The TrashPolicyDefault will use a floor and ceiling function to ensure that the Trash will be checkpointed every "interval" of minutes.
> Each user's trash is checkpointed individually. The time resolution of the checkpoint timestamp is to the second.
> If the seconds switch while one user is checkpointing, then the next user's timestamp will be later.
> This will cause the next user's checkpoint to not be deleted at the next interval.
> I have recreated this in a lab cluster
> I also have a suggestion for a patch that I can upload later tonight after testing it further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)