Ambari
  1. Ambari
  2. AMBARI-2557

Ambari fails to add additional Namenode storage directories if space-delimited

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.3
    • Fix Version/s: 1.2.5
    • Component/s: ambari-web
    • Labels:
      None

      Description

      PROBLEM: When using Ambari UI to add second NameNode storage directory, Ambari fails to produce correct configuration in hdfs-site.xml

      STEPS TO REPRODUCE:

      1. Stop HDFS and MapReduce on the cluster
      2. Go to Ambari UI and navigate to Services Tab and select HDFS
      3. Click on Configs Tab under HDFS
      4. Add second NameNode storage directory using format below:

      /hadoop/hdfs/namenode
      /hadoop1/hdfs/namenode

      5. Save configuration
      6. Start HDFS

      ACTUAL BEHAVIOR: Ambari fails to start HDFS.

      EXPECTED BEHAVIOR: To be able to make configuration change and to start HDFS.

      Configuration in UI was done similar as during installation process - not using comma separated values. However, this is not transfered correctly to hdfs-site.xml. See below the configuration produced by Ambari:

      </property>
      <property>
      <name>dfs.name.dir</name>
      <value>/hadoop/hdfs/namenode
      /hadoop1/hdfs/namenode</value>
      </property>

      Please note that the values are not comma separated as needed for correct configuration to work.

      I was able to make configuration work by making following config in UI:

      /hadoop/hdfs/namenode,/hadoop1/hdfs/namenode

      This produced correct config in hdfs-site.xml.

      Please note that during installation input values entering one location per line and produces correct configuration. Also, there is no guidance in UI to specify how to configure this correctly.

      1. AMBARI-2557.patch
        1 kB
        Andrii Babiichuk

        Activity

        Andrii Babiichuk created issue -
        Andrii Babiichuk made changes -
        Field Original Value New Value
        Attachment AMBARI-2557.patch [ 12590664 ]
        Andrii Babiichuk made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Yusaku Sako made changes -
        Description PROBLEM: When using Ambari UI to add second NameNode storage directory, Ambari fails to produce correct configuration in hdfs-site.xml

        BUSINESS IMPACT: users might not be able to take advantage of the feature and add second NameNode storage directory.

        STEPS TO REPRODUCE:

        1. Stop HDFS and MapReduce on the cluster
        2. Go to Ambari UI and navigate to Services Tab and select HDFS
        3. Click on Configs Tab under HDFS
        4. Add second NameNode storage directory using format below:

        /hadoop/hdfs/namenode
        /hadoop1/hdfs/namenode

        5. Save configuration
        6. Start HDFS

        ACTUAL BEHAVIOR: Ambari fails to start HDFS.

        EXPECTED BEHAVIOR: To be able to make configuration change and to start HDFS.

        SUPPORT ANALYSIS:

        Configuration in UI was done similar as during installation process - not using comma separated values. However, this is not transfered correctly to hdfs-site.xml. See below the configuration produced by Ambari:

        </property>
            <property>
            <name>dfs.name.dir</name>
            <value>/hadoop/hdfs/namenode
        /hadoop1/hdfs/namenode</value>
          </property>


        Please note that the values are not comma separated as needed for correct configuration to work.

        I was able to make configuration work by making following config in UI:

        /hadoop/hdfs/namenode,/hadoop1/hdfs/namenode


        This produced correct config in hdfs-site.xml.

        Please note that during installation input values entering one location per line and produces correct configuration. Also, there is no guidance in UI to specify how to configure this correctly.
        PROBLEM: When using Ambari UI to add second NameNode storage directory, Ambari fails to produce correct configuration in hdfs-site.xml

        STEPS TO REPRODUCE:

        1. Stop HDFS and MapReduce on the cluster
        2. Go to Ambari UI and navigate to Services Tab and select HDFS
        3. Click on Configs Tab under HDFS
        4. Add second NameNode storage directory using format below:

        /hadoop/hdfs/namenode
        /hadoop1/hdfs/namenode

        5. Save configuration
        6. Start HDFS

        ACTUAL BEHAVIOR: Ambari fails to start HDFS.

        EXPECTED BEHAVIOR: To be able to make configuration change and to start HDFS.

        Configuration in UI was done similar as during installation process - not using comma separated values. However, this is not transfered correctly to hdfs-site.xml. See below the configuration produced by Ambari:

        </property>
            <property>
            <name>dfs.name.dir</name>
            <value>/hadoop/hdfs/namenode
        /hadoop1/hdfs/namenode</value>
          </property>


        Please note that the values are not comma separated as needed for correct configuration to work.

        I was able to make configuration work by making following config in UI:

        /hadoop/hdfs/namenode,/hadoop1/hdfs/namenode


        This produced correct config in hdfs-site.xml.

        Please note that during installation input values entering one location per line and produces correct configuration. Also, there is no guidance in UI to specify how to configure this correctly.
        Yusaku Sako made changes -
        Summary Ambari fails to add second Namenode storage directory Ambari fails to add additional Namenode storage directories if space-delimited
        Yusaku Sako made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Andrii Babiichuk
            Reporter:
            Andrii Babiichuk
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development