Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 21 Mar 2014 20:57:59 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12546303.1331673491637.121364.1395435479940@arcas>
In-Reply-To: <JIRA.12546303.1331673491637@arcas>
References: <JIRA.12546303.1331673491637@arcas>
Subject: [jira] [Updated] (HDFS-3087) Decomissioning on NN restart can
 complete without blocks being replicated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee updated HDFS-3087:
-----------------------------

     Target Version/s: 2.5.0
    Affects Version/s:     (was: 0.24.0)
        Fix Version/s:     (was: 0.23.4)
                           (was: 0.23.2)
                           (was: 0.24.0)
                           (was: 0.23.0)
             Assignee:     (was: Kihwal Lee)

> Decomissioning on NN restart can complete without blocks being replicated
> -------------------------------------------------------------------------
>
>                 Key: HDFS-3087
>                 URL: https://issues.apache.org/jira/browse/HDFS-3087
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.23.0
>            Reporter: Kihwal Lee
>            Priority: Critical
>         Attachments: HDFS-3087.patch
>
>
> If a data node is added to the exclude list and the name node is restarted, the decomissioning happens right away on the data node registration. At this point the initial block report has not been sent, so the name node thinks the node has zero blocks and the decomissioning completes very quick, without replicating the blocks on that node.


--
This message was sent by Atlassian JIRA
(v6.2#6252)