[AMBARI-12347] AMS does not work with Kerberization in distrbuted mode

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.1
• Component/s: ambari-metrics
• Assignee: Dmytro Sen
• Reporter: Siddharth Wagle
• Created: 09/Jul/15 00:21
• Updated: 24/Jul/15 20:27
• Resolved: 24/Jul/15 18:14

Description

STR:

• Setup AMS in distributed mode
• Enable Kerberos using the Security wizard
• AMS fails to start with following log messages:

/var/log/ambari-metrics-collector/ambari-metrics-collector.log:

22:36:44,699 ERROR [main] ConnectionManager$HConnectionImplementation:879 - The node /ams-hbase-secure is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master.

/var/log/ambari-metrics-collector/hbase-ams-master-ambari-sid-3.log:

2015-07-08 22:51:08,626 WARN  [main] zookeeper.RecoverableZooKeeper: Possibly transient ZooKeeper, quorum=ambari-sid-3.c.pramod-thangali.internal:61181, exception=org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /ams-hbase-secure
2015-07-08 22:51:08,626 ERROR [main] zookeeper.RecoverableZooKeeper: ZooKeeper create failed after 4 attempts
2015-07-08 22:51:08,626 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMaster

Issue Links

• is related to: ZOOKEEPER-1811 The ZooKeeperSaslClient service name principal is hardcoded to "zookeeper"
• links to: Review Board