You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2017/04/28 15:44:04 UTC
[jira] [Assigned] (HDFS-11714) Newly added NN storage directory
won't get initialized and cause space exhaustion
[ https://issues.apache.org/jira/browse/HDFS-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kihwal Lee reassigned HDFS-11714:
---------------------------------
Assignee: Kihwal Lee
> Newly added NN storage directory won't get initialized and cause space exhaustion
> ---------------------------------------------------------------------------------
>
> Key: HDFS-11714
> URL: https://issues.apache.org/jira/browse/HDFS-11714
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.3
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Critical
> Attachments: HDFS-11714.trunk.patch
>
>
> When an empty namenode storage directory is detected on normal NN startup, it may not be fully initialized. The new directory is still part of "in-service" NNStrage and when a checkpoint image is uploaded, a copy will also be written there. However, the retention manager won't be able to purge old files since it is lacking a VERSION file. This causes fsimages to pile up in the directory. With a big name space, the disk will be filled in the order of days or weeks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org