[
https://issues.apache.org/jira/browse/HDFS-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902894#comment-14902894
]
Colin Patrick McCabe commented on HDFS-9105:
--------------------------------------------
I think it makes more sense to use the existing configuration option,
{{dfs.client.block.write.replace-datanode-on-failure.best-effort}}, instead.
Setting this configuration option will allow you to successfully close the
repl=2 file even if it can only be replicated to 1 DN.
> separate replication config for client to create a file or set replication
> --------------------------------------------------------------------------
>
> Key: HDFS-9105
> URL: https://issues.apache.org/jira/browse/HDFS-9105
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: HDFS-9105.patch
>
>
> one scenario when we want this new config: we want to enforce min replication
> of value 2, when client try to create a file, it's check against the
> replication factor of the new config, which is set to 2, so that client can
> not create a file of replication of 1. But when client try to close file and
> there are some datanode failures in the pipeline and only 1 datanode remain,
> it is checked against old minReplication value, which has value 1, so we will
> allow client to close the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
