Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- Is contained by
-
AMBARI-15507 Support for Multiple Nameservices
- Resolved
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-15615adds that parameter to the HDFS service with 2.4.0