@vrathod As this issue is resolved then please mark the answer as "Accepted". ... View more

@Elvis Zhang It is strange to see the following error: [WARNING] emitter.py:84 - Error sending metrics to server. [Errno 113] No route to host . Which means the ambari metrics monitors are not able to communicate to AMS collector on the mentioned port. hence the data (memory/CPU ...etc) are not being emitted. Can you please check if from the metrics monitor host you are able to connect to AMS collector host/port (Just to see that there is no Firewall restriction on the port.) # telnet bn-003.hadoop 6188 . Also are the FQDNs correctly configured through out the cluster. So that you get the correct hostname in the following command output: # hostname -f . Also please see: http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-installation/content/set_the_hostname.html and http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-installation/content/edit_the_network_configuration_file.html ... View more

@Elvis Zhang If you have just added AMS to your cluster then the services need to be restarted to initiate the Sink. That is controlled by metrics properties file like: # cat /etc/hadoop/conf/hadoop-metrics2.properties Also in the NameNode (DataNode) logs do you see that the "Sink timeline started" is started as following: # less /var/log/hadoop/hdfs/hadoop-hdfs-namenode-erie1.example.com.log INFO timeline.HadoopTimelineMetricsSink (HadoopTimelineMetricsSink.java:init(82)) - Initializing Timeline metrics sink. INFO timeline.HadoopTimelineMetricsSink (HadoopTimelineMetricsSink.java:init(100)) - Identified hostname = erie1.example.com, serviceName = namenode INFO timeline.HadoopTimelineMetricsSink (HadoopTimelineMetricsSink.java:init(118)) - Collector Uri: <a href="http://erie2.example.com:6188/ws/v1/timeline/metrics">http://erie2.example.com:6188/ws/v1/timeline/metrics</a> INFO timeline.HadoopTimelineMetricsSink (HadoopTimelineMetricsSink.java:init(166)) - RPC port properties configured: {8020=client} NFO impl.MetricsSinkAdapter (MetricsSinkAdapter.java:start(206)) - Sink timeline started ... View more

@Elvis Zhang In the following log file do you see any error? /var/log/ambari-metrics-collector/ambari-metrics-collector.log . What is the ambari server ambari metrics collector version? Is it same on all hosts? Are you seeing the same version for all AMS & ambari components? # rpm -qa | grep ambari* . ... View more

@vrathod The driver jar might have been deleted accidentally. As i have never seen such issue earlier, there is no existing JIRA as well on the similar issue. So i am suspecting that it might be deleted accidentally. ... View more

@Micaël Dias Are you able to access the port where you are getting the "connection to broker kafka.host.com:6667 (id: 1003 rack: null) was unsuccessful" error "Failed to find leader for Set([newmikl,0]) (kafka.consumer.ConsumerFetcherManager$LeaderFinderThread)" ? telnet kafka.host.com 6667 . On the kafka broker host please verify if the port is opened. Example: # netstat -tnlpa | grep 6667 tcp 0 0 ::ffff:172.26.70.154:6667 :::* LISTEN 15573/java tcp 0 0 ::ffff:172.26.70.154:6667 ::ffff:172.26.70.154:48623 ESTABLISHED 15573/java tcp 0 0 ::ffff:172.26.70.154:48623 ::ffff:172.26.70.154:6667 ESTABLISHED 15573/java . ... View more