You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2014/08/13 17:46:13 UTC

[jira] [Updated] (HDFS-6016) Update datanode replacement policy to make writes more robust

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

Kihwal Lee updated HDFS-6016:
-----------------------------

    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

Per Nicholas' comment, I won't fix it.

> 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)