After upgrading to Ambari 2.0, the Ganglia service stays intact in cluster. You must perform the following steps to remove Ganglia from the cluster and to move to the new Ambari Metrics system.
Important | |
---|---|
|
Stop Ganglia service via Ambari Web.
Using the Ambari REST API, remove the Ganglia service by executing the following:
curl -u <admin_user_name>:<admin_password> -H 'X-Requested-By:ambari' -X DELETE 'http://<ambari_server_host>:8080/api/v1/clusters/<cluster_name>/services/GANGLIA'
Refresh Ambari Web and make sure that Ganglia service is no longer visible.
In the Actions menu on the left beneath the list of Services, use the "Add Service" wizard to add
Ambari Metrics
to the cluster.This will install an
Ambari Metrics Collector
into the cluster, and anAmbari Metrics Monitor
on each host.Pay careful attention to following service configurations:
Section
Property
Description
Default Value
Advanced ams-hbase-site
hbase.rootdir
Ambari Metrics service uses HBase as default storage backend. Set the rootdir for HBase to either local filesystem path if using Ambari Metrics in embedded mode or to a HDFS dir. For example: hdfs://namenode.example.org:8020/amshbase.
file://var/lib/ambari-metrics-collector/hbase
For the cluster services to start sending metrics to Ambari Metrics, restart all services. For example, restart HDFS, YARN, HBase, Flume, Storm and Kafka.
Note | |
---|---|
(Optional) Remove the Ganglia packages (ganglia-gmetad and ganglia-gmond) from the hosts. |
Important | |
---|---|
If you are managing a HDP 2.2 cluster that includes Kafka, you must adjust the Kafka configuration to send metrics to the Ambari Metrics system. From Ambari Web, browse to
|