You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Zack Marsh (JIRA)" <ji...@apache.org> on 2015/06/05 01:19:38 UTC
[jira] [Updated] (AMBARI-11708) Ambari Metrics Collector not
running after enabling Kerberos
[ https://issues.apache.org/jira/browse/AMBARI-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zack Marsh updated AMBARI-11708:
--------------------------------
Description:
On an HDP 2.3.0.0 cluster using Ambari 2.1.0 Kerberos has been enabled via Ambari's Kerberos Wizard. Kerberos was enabled using an existing MIT KDC and the box for "Manage Kerberos client krb5.conf" was unchecked.
After the Kerberos Wizard completes and all of the Hadoop services are started, the Ambari Metrics Collector consistently stops running.
The ambari-metrics-collector.log [attached] is filled with the following error message:
{code}
18:16:27,431 INFO [main] ConnectionManager$HConnectionImplementation:1613 - getMaster attempt 23 of 35 failed; retrying after sleep of 20178, exception=org.apache.hadoop.hbase.MasterNotRunningException: 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.
{code}
The value for "zookeeper.znode.parent" in the Ambari Metrics Collector's hbase-site.xml is set to "/ams-hbase-secure".
I see that ams-hbase-secure is not in Zookeeper:
{code}
[zk: localhost:2181(CONNECTED) 0] ls /
[hive, hiveserver2, zookeeper, hbase-unsecure, yarn-leader-election, hadoop-ha, oozie, rmstore, hbase-secure, services]
{code}
Is this something that should have been handled in Ambari's Kerberos Wizard?
was:
On an HDP 2.3.0.0 cluster using Ambari 2.1.0 Kerberos has been enabled via Ambari's Kerberos Wizard. Kerberos was enabled using an existing MIT KDC and the box for "Manage Kerberos client krb5.conf" was unchecked.
After the Kerberos Wizard completes and all of the Hadoop services are started, the Ambari Metrics Collector consistently stops running.
The ambari-metrics-collector.log is filled with the following error message:
{code}
18:16:27,431 INFO [main] ConnectionManager$HConnectionImplementation:1613 - getMaster attempt 23 of 35 failed; retrying after sleep of 20178, exception=org.apache.hadoop.hbase.MasterNotRunningException: 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.
{code}
The value for "zookeeper.znode.parent" in the Ambari Metrics Collector's hbase-site.xml is set to "/ams-hbase-secure".
I see that ams-hbase-secure is not in Zookeeper:
{code}
[zk: localhost:2181(CONNECTED) 0] ls /
[hive, hiveserver2, zookeeper, hbase-unsecure, yarn-leader-election, hadoop-ha, oozie, rmstore, hbase-secure, services]
{code}
Is this something that should have been handled in Ambari's Kerberos Wizard?
> Ambari Metrics Collector not running after enabling Kerberos
> ------------------------------------------------------------
>
> Key: AMBARI-11708
> URL: https://issues.apache.org/jira/browse/AMBARI-11708
> Project: Ambari
> Issue Type: Bug
> Environment: ambari-2.1.0-877, hdp-2.3.0.0-2223, sles11sp3
> Reporter: Zack Marsh
> Attachments: ambari-metrics-collector.log
>
>
> On an HDP 2.3.0.0 cluster using Ambari 2.1.0 Kerberos has been enabled via Ambari's Kerberos Wizard. Kerberos was enabled using an existing MIT KDC and the box for "Manage Kerberos client krb5.conf" was unchecked.
> After the Kerberos Wizard completes and all of the Hadoop services are started, the Ambari Metrics Collector consistently stops running.
> The ambari-metrics-collector.log [attached] is filled with the following error message:
> {code}
> 18:16:27,431 INFO [main] ConnectionManager$HConnectionImplementation:1613 - getMaster attempt 23 of 35 failed; retrying after sleep of 20178, exception=org.apache.hadoop.hbase.MasterNotRunningException: 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.
> {code}
> The value for "zookeeper.znode.parent" in the Ambari Metrics Collector's hbase-site.xml is set to "/ams-hbase-secure".
> I see that ams-hbase-secure is not in Zookeeper:
> {code}
> [zk: localhost:2181(CONNECTED) 0] ls /
> [hive, hiveserver2, zookeeper, hbase-unsecure, yarn-leader-election, hadoop-ha, oozie, rmstore, hbase-secure, services]
> {code}
> Is this something that should have been handled in Ambari's Kerberos Wizard?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)