[
https://issues.apache.org/jira/browse/HDFS-14586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869102#comment-16869102
]
Wu Weiwei commented on HDFS-14586:
----------------------------------
Great!
This problem has also occurred in our production environment. More than one day
of the checkpoint directory was retained, triggering an annoying alarm call,
and we had to manually delete the expired directory.
This patch can solve our problem.
> Trash missing delete the folder which near timeout checkpoint
> -------------------------------------------------------------
>
> Key: HDFS-14586
> URL: https://issues.apache.org/jira/browse/HDFS-14586
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: hu yongfa
> Priority: Major
> Attachments: HDFS-14586.001.patch
>
>
> when trash timeout checkpoint coming, trash will delete the old folder first,
> then create a new checkpoint folder.
> as the delete action may spend a long time, such as 2 minutes, so the new
> checkpoint folder created late.
> at the next trash timeout checkpoint, trash will skip delete the new
> checkpoint folder, because the new checkpoint folder is
> less than a checkpoint interval.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
