Uploaded image for project: 'CDH (READ-ONLY)'
  1. CDH (READ-ONLY)
  2. DISTRO-633

Fails trying to Enable High Availability when trying to start the secondary namenode

          Details

          • Type: Task
          • Status: Resolved
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: CDH4.6.0
          • Fix Version/s: None
          • Component/s: HDFS
          • Labels:
          • Environment:
            Version: Cloudera Enterprise 4.8.2 (#101 built by jenkins on 20140226-1855 git: 8609801079d228f2440a493a3880ab68cad0524b)

            Description

            History:
            See Attached Architecture Diagram.
            Cloudera 4.6 Enterprise is installed, configured and running currently without High Availability. No Health Issues logged.

            Issue:
            Trying to Enable High Availability and make the secondary master node to be the Standby Node. (as in the attachement).

            While in the Cloudera Manager gui, I clicked on
            Services --> HDFS1 --> Actions --> Enable High Availability

            It gets to Step 11 of 17 and then it just spins.
            It looked like the 2 master nodes went into Standby Mode and just sits.

            I attached snips of the screenshots and 2 logs on the secondary master node trying to start:

            ../cloudera-scm-agent.log
            ../hadoop-hdfs/hadoop-cmf-hdfs1-NAMENODE-qps06au.vsp.sas.com.log.out

            I am under the impression that the CM gui updates all the conf files (xml, etc.) behind the scenes as I click through the wizard, but IF there are manual steps and other files or connection tests that I need to be aware of please update me.

            Regards,
            Steve

              Attachments

                Activity

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    stagba Steve Agbayani
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: