You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2017/07/10 16:17:01 UTC
[jira] [Updated] (AMBARI-21279) Handle scenario when host in-memory
aggregation is not working
[ https://issues.apache.org/jira/browse/AMBARI-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen updated AMBARI-21279:
--------------------------------
Status: Open (was: Patch Available)
> 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
> 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
(v6.4.14#64029)