THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Configuration Type | File path | Comment |
|---|---|---|
| ams-env | /etc/ambari-metrics-monitor/conf/ams-env.sh | Used for log and pid dir modifications, this is the same configuration as above, common to both components. |
| metric_groups | /etc/ambari-metrics-monitor/conf/metric_groups.conf | Not available in the UI. Used to control what HOST/SYSTEM metrics are reported. |
| metric_monitor | /etc/ambari-metrics-monitor/conf/metric_monitor.ini | Not available in the UI. Settings for the monitor daemon. |
Configuring
...
Ambari Metrics service in distributed mode
In distributed mode, Metric Collector writes go to HDFS of the cluster. Currently distributed mode does not support multi-mode Metric Collector, however the plan is to allow Metric Collector to scale horizontally to allow a multi-node HBase storage layer.
...
- Edit ams-site, Set timeline.metrics.service.operation.mode = distributed
- Edit ams-hbase-site,
- Set hbase.rootdir = hdfs://<namenode-host>:8020/amshbase (Note: amshbase here is the directory where metric data will be stored in HDFS)
- Set hbase.cluster.distributed = true
Note: In Ambari 2.0, there is a bug in deploying AMS in distributed mode. Please follow the instruction listed in this JIRA as workaround steps: (AMBARI-10707)