[ https://issues.apache.org/jira/browse/HDFS-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874026#comment-13874026 ]
Eric Sirianni commented on HDFS-5434: ------------------------------------- Arpit - after some discussion, Buddy and I realized that the approach in HDFS-5769 can't be applied to solve the pipeline recovery problem. In a shared-storage environment, the R/O node only has access to the {{hsync()}}-ed data (the data actually flushed to the shared storage device). However, pipeline recovery must guarantee that all data that has been {{ACK}}'d can be recovered. Therefore, recruiting a R/O node into a pipeline (as HDFS-5769 suggests) will not work for this case. Is our understanding correct? (If so I will also update HDFS-5769 accordingly) > Write resiliency for replica count 1 > ------------------------------------ > > Key: HDFS-5434 > URL: https://issues.apache.org/jira/browse/HDFS-5434 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.2.0 > Reporter: Buddy > Priority: Minor > Attachments: BlockPlacementPolicyMinPipelineSize.java, > BlockPlacementPolicyMinPipelineSizeWithNodeGroup.java, > HDFS-5434-branch-2.patch, HDFS_5434.patch > > > If a file has a replica count of one, the HDFS client is exposed to write > failures if the data node fails during a write. With a pipeline of size of > one, no recovery is possible if the sole data node dies. > A simple fix is to force a minimum pipeline size of 2, while leaving the > replication count as 1. The implementation for this is fairly non-invasive. > Although the replica count is one, the block will be written to two data > nodes instead of one. If one of the data nodes fails during the write, normal > pipeline recovery will ensure that the write succeeds to the surviving data > node. > The existing code in the name node will prune the extra replica when it > receives the block received reports for the finalized block from both data > nodes. This results in the intended replica count of one for the block. > This behavior should be controlled by a configuration option such as > {{dfs.namenode.minPipelineSize}}. > This behavior can be implemented in {{FSNameSystem.getAdditionalBlock()}} by > ensuring that the pipeline size passed to > {{BlockPlacementPolicy.chooseTarget()}} in the replication parameter is: > {code} > max(replication, ${dfs.namenode.minPipelineSize}) > {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)