[
https://issues.apache.org/jira/browse/HDFS-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8118:
--------------------------
Hadoop Flags: Reviewed
Affects Version/s: 2.7.1
Target Version/s: 3.0.0, 2.8.0
Status: Patch Available (was: Open)
I re-looked at the change and the problem, and although this can be difficult
to test, the change does certainly fix the described changing-timestamp
behaviour.
+1, will commit after verifying Jenkins result on the newer patch. Marking as
Patch Available to trigger the build.
> Delay in checkpointing Trash can leave trash for 2 intervals before deleting
> ----------------------------------------------------------------------------
>
> Key: HDFS-8118
> URL: https://issues.apache.org/jira/browse/HDFS-8118
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Casey Brotherton
> Assignee: Casey Brotherton
> Priority: Trivial
> 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)
