[
https://issues.apache.org/jira/browse/HDFS-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5020:
----------------------------
Description: 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.
(was: Currently DatanodeProtocol#blockReceivedAndDeleted is not idempotent
because pending replication maps in NN only tracks the number of the pending
replicas, and a retry request can cause the pending number decreased more than
once. We can make blockReceivedAndDeleted idempotent by tracking corresponding
datanodes in the pending replication map. )
> 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
>
> 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
