[jira] [Commented] (AMBARI-21279) Handle scenario when host in-memory aggregation is not working

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075611#comment-16075611 ] 

Hadoop QA commented on AMBARI-21279:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12873493/AMBARI-21279.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-metrics/ambari-metrics-timelineservice.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11719//console

This message is automatically generated.

> 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.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)