hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11714) Newly added NN storage directory won't get initialized and cause space exhaustion
Date Fri, 28 Apr 2017 18:03:04 GMT

     [ 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.v2.trunk.patch

Attaching updated patches. Everything is confined in FSImage as you suggested. I think it
is safe.  The branch-2 patch only differs slightly in the new test.

> 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, HDFS-11714.v2.branch-2.patch, HDFS-11714.v2.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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message