You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Henning Kropp (JIRA)" <ji...@apache.org> on 2016/04/04 15:39:25 UTC
[jira] [Commented] (AMBARI-15509) Install with Multiple
Nameservices can result in DN register with wrong cluster
[ https://issues.apache.org/jira/browse/AMBARI-15509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224130#comment-15224130 ]
Henning Kropp commented on AMBARI-15509:
----------------------------------------
According to this patch https://issues.apache.org/jira/browse/HDFS-6376 since Hadoop 2.6 the parameter {{dfs.internal.nameservices}} needs to be set in hdfs-site. AMBARI-15615 adds that parameter to the HDFS service with 2.4.0
> Install with Multiple Nameservices can result in DN register with wrong cluster
> -------------------------------------------------------------------------------
>
> Key: AMBARI-15509
> URL: https://issues.apache.org/jira/browse/AMBARI-15509
> Project: Ambari
> Issue Type: Bug
> Reporter: Henning Kropp
>
> It was experienced that during an install using a blueprint the DN's registered with the wrong cluster when multiple nameservices are defined in {{hdfs_site\[dfs.nameservices\]}}
> This needs verification how the instlal process might lead to such an outcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)