> On Апрель 18, 2016, 1:39 п.п., Robert Nettleton wrote:
> > Could we get some more background context as to why this change is 
> > necessary?  I've checked the associated Apache JIRA, and there isn't much 
> > information there.
> > 
> > In particular, can the submitter please explain why this internal property 
> > needs to be added, especially considering that the HDFS documentation seems 
> > to indicate that the public and internal forms of this property should 
> > generally have the same value? 
> > 
> > Thanks.

HDFS-6376 allows distcp to copy data between HA clusters. Users can use a new 
configuration property "dfs.internal.nameservices" to explicitly specify the 
name services belonging to the local cluster, while continue using the 
configuration property "dfs.nameservices" to specify all the name services in 
the local and remote clusters.

All ambari users have single namesevice value in "dfs.nameservices" on existing 
clusters, that's the name service belonging to the local cluster. After upgrade 
to 2.4.0 or restoring ambari cluster from a blueprint created from any older 
version, we add "dfs.internal.nameservices" pointing to the local cluster and 
allow user to add to "dfs.nameservices" any external name services.


- Dmytro


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46327/#review129331
-----------------------------------------------------------


On Апрель 18, 2016, 1:39 п.п., Dmytro Sen wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/46327/
> -----------------------------------------------------------
> 
> (Updated Апрель 18, 2016, 1:39 п.п.)
> 
> 
> Review request for Ambari, John Speidel and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-15791
>     https://issues.apache.org/jira/browse/AMBARI-15791
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Blueprint config processing engine should automatically populate 
> dfs.internal.nameservices when it is deploying HA clusters. The work-around 
> till then is to explicitly add the property when submitting the blueprint.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
>  1433a1b 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
>  834953b 
> 
> Diff: https://reviews.apache.org/r/46327/diff/
> 
> 
> Testing
> -------
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Reply via email to