[ 
https://issues.apache.org/jira/browse/HDFS-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170210#comment-16170210
 ] 

Yongjun Zhang commented on HDFS-11799:
--------------------------------------

Thanks for the updated patch [~brahmareddy], +1 pending the following nit and 
jenkins test:
{code}
323       String  MIN_REPLICATION = PREFIX + "min-replication";
324       short  REPLICATION_DEFAULT = 0;
{code}
The config and default value variable names are not consistent.  Suggest to 
change the default value to {{MIN_REPLICATION_DEFAULT}}.


> 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
>            Assignee: Brahma Reddy Battula
>         Attachments: HDFS-11799-002.patch, HDFS-11799-003.patch, 
> HDFS-11799-004.patch, HDFS-11799-005.patch, HDFS-11799-006.patch, 
> HDFS-11799-007.patch, 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to