[
https://issues.apache.org/jira/browse/HDFS-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963516#comment-13963516
]
Tsz Wo Nicholas Sze commented on HDFS-6016:
-------------------------------------------
> ... Making it also add additional DN when r == 2 and the current number of
> DNs is 1.
When creating a file with r == 2, the user actually cares more about the
performance. (Otherwise, one should use r == 3.) Also, if datanode
replacement is preferred, one could set the policy to ALWAYS. So I suggest
don't make this change.
> Update datanode replacement policy to make writes more robust
> -------------------------------------------------------------
>
> Key: HDFS-6016
> URL: https://issues.apache.org/jira/browse/HDFS-6016
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, ha, hdfs-client, namenode
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-6016.patch, HDFS-6016.patch
>
>
> As discussed in HDFS-5924, writers that are down to only one node due to node
> failures can suffer if a DN does not restart in time. We do not worry about
> writes that began with single replica.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
