Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-15509

Install with Multiple Nameservices can result in DN register with wrong cluster

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.4.0
    • 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

        1. c1_ha_two_nameservices.txt
          36 kB
          Dmytro Sen

        Issue Links

          Activity

            hkropp Henning Kropp added a comment -

            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

            hkropp Henning Kropp added a comment - 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
            dsen Dmytro Sen added a comment -

            This issue was fixed in the scope of AMBARI-15507.
            I was able to deploy a cluster from the blueprint attached to this jira, where hdfs_site[dfs.nameservices] == 'my,ext'

            dsen Dmytro Sen added a comment - This issue was fixed in the scope of AMBARI-15507 . I was able to deploy a cluster from the blueprint attached to this jira, where hdfs_site [dfs.nameservices] == 'my,ext'

            People

              dsen Dmytro Sen
              hkropp Henning Kropp
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: