Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 7 Aug 2014 03:38:12 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12732458.1407382661214.31565.1407382692956@arcas>
In-Reply-To: <JIRA.12732458.1407382661214@arcas>
References: <JIRA.12732458.1407382661214@arcas>
Subject: [jira] [Created] (HDFS-6830) BlockManager.addStorage fails when DN
 updates storage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Arpit Agarwal created HDFS-6830:
-----------------------------------

             Summary: BlockManager.addStorage fails when DN updates storage
                 Key: HDFS-6830
                 URL: https://issues.apache.org/jira/browse/HDFS-6830
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 2.5.0
            Reporter: Arpit Agarwal
            Assignee: Arpit Agarwal


The call to {{removeStorageInfo}} is wrong because the block is still in the DatanodeStorage's list of blocks and the callee does not expect it to be.

{code}
      } else {
        // The block is on the DN but belongs to a different storage.
        // Update our state.
        removeStorage(getStorageInfo(idx));
        added = false;      // Just updating storage. Return false.
      }
{code}

It is a very unlikely code path to hit since storage updates usually occur via incremental block reports.


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