[
https://issues.apache.org/jira/browse/HDFS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HDFS-1606:
-----------------------------------------
Resolution: Fixed
Release Note: Added two configuration properties,
dfs.client.block.write.replace-datanode-on-failure.enable and
dfs.client.block.write.replace-datanode-on-failure.policy. Added a new feature
to replace datanode on failure in DataTransferProtocol. Added
getAdditionalDatanode(..) in ClientProtocol.
Hadoop Flags: [Incompatible change, Reviewed]
Status: Resolved (was: Patch Available)
Thanks Jitendra for the review.
I have committed this.
> Provide a stronger data guarantee in the write pipeline
> -------------------------------------------------------
>
> Key: HDFS-1606
> URL: https://issues.apache.org/jira/browse/HDFS-1606
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: data-node, hdfs client, name-node
> Affects Versions: 0.23.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.23.0
>
> Attachments: h1606_20110210.patch, h1606_20110211.patch,
> h1606_20110217.patch, h1606_20110228.patch, h1606_20110404.patch,
> h1606_20110405.patch, h1606_20110405b.patch, h1606_20110406.patch,
> h1606_20110406b.patch, h1606_20110407.patch, h1606_20110407b.patch,
> h1606_20110407c.patch, h1606_20110408.patch, h1606_20110408b.patch
>
>
> In the current design, if there is a datanode/network failure in the write
> pipeline, DFSClient will try to remove the failed datanode from the pipeline
> and then continue writing with the remaining datanodes. As a result, the
> number of datanodes in the pipeline is decreased. Unfortunately, it is
> possible that DFSClient may incorrectly remove a healthy datanode but leave
> the failed datanode in the pipeline because failure detection may be
> inaccurate under erroneous conditions.
> We propose to have a new mechanism for adding new datanodes to the pipeline
> in order to provide a stronger data guarantee.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
