Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 23 Jul 2013 08:42:49 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12659229.1374536801183.95851.1374568969790@arcas>
In-Reply-To: <JIRA.12659229.1374536801183@arcas>
References: <JIRA.12659229.1374536801183@arcas>
Subject: [jira] [Updated] (HDFS-5020) Make
 DatanodeProtocol#blockReceivedAndDeleted idempotent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jing Zhao updated HDFS-5020:
----------------------------

    Attachment: HDFS-5020.002.patch

Fix the failed test and add a new unit test.
                
> Make DatanodeProtocol#blockReceivedAndDeleted idempotent
> --------------------------------------------------------
>
>                 Key: HDFS-5020
>                 URL: https://issues.apache.org/jira/browse/HDFS-5020
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-5020.001.patch, HDFS-5020.002.patch
>
>
> Currently DatanodeProtocol#blockReceivedAndDeleted is not idempotent because pending replication maps in NN only tracks the number of the pending replicas, and a retry request about a received block can cause the pending number decreased more than once. We can make blockReceivedAndDeleted idempotent by tracking corresponding datanodes in the pending replication map. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira