[
https://issues.apache.org/jira/browse/HDFS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910024#comment-16910024
]
Wei-Chiu Chuang commented on HDFS-10606:
----------------------------------------
I am not sure I understand the problem statement. It's probably just a matter
of English translation though.
bq. In the most serious situations it may lead some cron job submit failure. if
add configuration about time of cleaning up, it will avoid impact on this cron
jobs at that default time.
I understand NN may choke on a large trash directory cleanup, but it seems the
patch just extend the trash emptier thread sleep time. It's not that clear to
me how this is going to remedy the problem.
Additionally, is HDFS-13529 or HDFS-14586related in any ways?
> TrashPolicyDefault supports time of auto clean up can configured
> ----------------------------------------------------------------
>
> Key: HDFS-10606
> URL: https://issues.apache.org/jira/browse/HDFS-10606
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.7.0
> Reporter: He Xiaoqiao
> Assignee: He Xiaoqiao
> Priority: Major
> Attachments: HDFS-10606-branch-2.7.001.patch, HDFS-10606.001.patch,
> HDFS-10606.002.patch
>
>
> TrashPolicyDefault clean up Trash based on
> [UTC|http://www.worldtimeserver.com/current_time_in_UTC.aspx] currently and
> the time of cleaning up is 00:00 UTC. when there are large amount of trash
> data should be auto-clean, it will block NN for a long time since Global
> Lock, In the most serious situations it may lead some cron job submit
> failure. if add configuration about time of cleaning up, it will avoid impact
> on this cron jobs at that default time.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
