[
https://issues.apache.org/jira/browse/HDFS-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005181#comment-16005181
]
Brahma Reddy Battula edited comment on HDFS-11799 at 5/11/17 6:13 AM:
----------------------------------------------------------------------
[~yzhangal] Nice Idea..
Configuration can be
{{dfs.client.block.write.replace-datanode-on-failure.replication}} ..?
We had similar approach which was used for small cluster..will update patch
tomorrow.
was (Author: brahmareddy):
[~yzhangal] Nice Idea..
Configuration can be
{{dfs.client.block.write.replace-datanode-on-failure.replication}} ..?
We had similar approach which was used for small cluster..will update patch
tomorrow.,if you dn't mind..
> Introduce a config to allow setting up write pipeline with fewer nodes than
> replication factor
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-11799
> URL: https://issues.apache.org/jira/browse/HDFS-11799
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Yongjun Zhang
> Attachments: HDFS-11799.patch
>
>
> During pipeline recovery, if not enough DNs can be found, if
> dfs.client.block.write.replace-datanode-on-failure.best-effort
> is enabled, we let the pipeline to continue, even if there is a single DN.
> Similarly, when we create the write pipeline initially, if for some reason we
> can't find enough DNs, we can have a similar config to enable writing with a
> single DN.
> More study will be done.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
