hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5020) Make DatanodeProtocol#blockReceivedAndDeleted idempotent
Date Wed, 24 Jul 2013 07:37:49 GMT

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

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

       Resolution: Fixed
    Fix Version/s: 2.1.0-beta
           Status: Resolved  (was: Patch Available)

Thanks for the review Chris! I've committed this to trunk, branch-2 and branch-2.1-beta.
                
> Make DatanodeProtocol#blockReceivedAndDeleted idempotent
> --------------------------------------------------------
>
>                 Key: HDFS-5020
>                 URL: https://issues.apache.org/jira/browse/HDFS-5020
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>             Fix For: 2.1.0-beta
>
>         Attachments: HDFS-5020.001.patch, HDFS-5020.002.patch, HDFS-5020.003.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

Mime
View raw message