[
https://issues.apache.org/jira/browse/AMBARI-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421782#comment-16421782
]
Hudson commented on AMBARI-21279:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8958 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8958/])
AMBARI-21279 Handle scenario when host in-memory aggregation is not (avijayan:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=4efcf9d9f22131e0afcd1e46de14660f18d2f00e])
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricsService.java
* (add)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricFilteringHostAggregator.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/SplitByMetricNamesCondition.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultCondition.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/EmptyCondition.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/Condition.java
* (add)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/v2/TimelineMetricFilteringHostAggregator.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricAggregatorFactory.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataManager.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestPhoenixTransactSQL.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultConditionTest.java
> Handle scenario when host in-memory aggregation is not working
> --------------------------------------------------------------
>
> Key: AMBARI-21279
> URL: https://issues.apache.org/jira/browse/AMBARI-21279
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
> Affects Versions: 3.0.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: AMBARI-21279_2.patch
>
>
> If monitor aggregation is enabled we do not do collector side 5 minutes
> aggregation. If a monitor is down we do not get metrics from that host.
> Metrics collector should check that metrics from a host are available per
> minute but aggregates are not.
> This could be based on liveliness check of a monitor. More like a heartbeat
> ping. When we loose ping for > 1 min < 5 min we can aggregate metrics for
> that time period and hostId.
> Sinks and monitor should switch back to collector reporting state if local
> aggregation app is not available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
