Hi PD, This is a known bug in AMS. The cause is that AMS uses its own instance of Yarn ATS as the application server, and has the cluster core-site in its conf directory (/etc/ambari-metrics-collector/conf). Since the core-site has spnego configs used by cluster Hadoop components, this ATS picks them up, and acts as a spnego enabled end point, even though AMS has no spnego support. The workaround fix (https://issues.apache.org/jira/browse/AMBARI-18187) was recently checked into branch-2.4, and should be part of next Ambari release - 2.4.2. The long term solution of supporting SPNEGO in AMS is being worked on as part of https://issues.apache.org/jira/browse/AMBARI-14384, and is planned for Ambari-2.5.0. ... View more

Hi @ARUN, Please clear the contents of /var/lib/ambari-metrics-collector/hbase-tmp/zookeeper/* and restart Ambari metrics collector. Let me know if that works! Thanks ... View more

What version of Ambari is this? I assume the value of your config item in ams-site : "timeline.metrics.service.operation.mode" is embedded. Please verify the config ams-hbase-site : hbase.cluster.distributed = false. If both of these configs are as stated above, and you still get an error for hbase.rootdir = file:///local/var/lib/ambari-metrics-collector/hbase, please omit the warning and go ahead the deploy the services. Also, please share the screenshot for the warning you see so that we can create a bug to track it. In general, AMS operates in 2 modes. embedded : Single AMS HBase daemon writing to local disk. distributed : Separate AMS HBase master and RS daemons by default writing to HDFS. ... View more

Could be because of https://issues.apache.org/jira/browse/AMBARI-15492. This has been fixed in the next Ambari release (2.2.2). For a workaround please try commenting these 2 properties in /etc/ambari-server/conf/ambari.properties #recovery.enabled_components=METRICS_COLLECTOR #recovery.type=AUTO_START Restart Ambari Server. ... View more