[ https://issues.apache.org/jira/browse/HDFS-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kihwal Lee updated HDFS-11714: ------------------------------ Attachment: HDFS-11714.trunk.patch The version file can be created in an empty storage diectory in other ways. Doing a full upgrade or finalizing a rolling upgrade will cause unconditional write of VERSION to all storage directories. Attaching a patch. It saves any new directory to a set and when a checkpoint is written, a VERSION file is also written. This is roughly equivalent to the non-HA mechanism of doing {{saveNamespace()}} causing creation of a VERSION file. > 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 > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org