hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (HADOOP-12352) Delay in checkpointing Trash can leave trash for 2 intervals before deleting
Date Tue, 25 Aug 2015 05:49:47 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-12352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Harsh J moved HDFS-8118 to HADOOP-12352:

    Affects Version/s:     (was: 2.7.1)
     Target Version/s: 2.8.0, 3.0.0  (was: 3.0.0, 2.8.0)
                  Key: HADOOP-12352  (was: HDFS-8118)
              Project: Hadoop Common  (was: Hadoop HDFS)

> 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
>         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

This message was sent by Atlassian JIRA

View raw message