[
https://issues.apache.org/jira/browse/HDFS-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991705#comment-15991705
]
Hudson commented on HDFS-11714:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11663 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11663/])
HDFS-11714. Newly added NN storage directory won't get initialized and (kihwal:
rev 4cfc8664362ed04b01872e854715a36dad9408a6)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestStandbyCheckpoints.java
> 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
> Fix For: 2.7.4, 3.0.0-alpha3, 2.8.1
>
> Attachments: HDFS-11714.trunk.patch, HDFS-11714.v2.branch-2.patch,
> HDFS-11714.v2.trunk.patch, HDFS-11714.v3.branch-2.patch,
> HDFS-11714.v3.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: [email protected]
For additional commands, e-mail: [email protected]
