Page History

...

Note: In Ambari 2.0, there is a bug in deploying AMS in distributed mode, if Namenode HA is enabled. Please follow the instruction listed in this JIRA as workaround steps: (AMBARI-10707)

Metric Collector - ams-site - Configuration details

• Modifying retention interval for time aggregated data.
  (Note: In Ambari 2.0 and 2.1, the Phoenix version does not support Alter TTL queries. So these can be modified from the UI only at install time. Please refer to Known Issues section for workaround.)

  Property	Default Value	Description
  timeline.metrics.host.aggregator.ttl	86400	1 minute resolution data purge interval. Default is 1 day.
  timeline.metrics.host.aggregator.minute.ttl	604800	Host based X minutes resolution data purge interval. (X = configurable, default is 5 minutes) Default is 7 days.
  timeline.metrics.host.aggregator.hourly.ttl	2592000	Host based hourly resolution data purge interval. Default is 30 days.
  timeline.metrics.host.aggregator.daily.ttl	31536000	Host based daily resolution data purge interval. Default is 1 year.
  timeline.metrics.cluster.aggregator.minute.ttl	2592000	Cluster wide minute resolution data purge interval. Default is 30 days.
  timeline.metrics.cluster.aggregator.hourly.ttl	31536000	Cluster wide hourly resolution data purge interval. Default is 1 year.
  timeline.metrics.cluster.aggregator.daily.ttl	63072000	Cluster wide daily resolution data purge interval. Default is 2 years.

  
  
  

•