ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20758) Aggregate local metrics for minute aggregation time window
Date Thu, 13 Apr 2017 17:26:41 GMT

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

Hadoop QA commented on AMBARI-20758:
------------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 23 new or modified
test files.

        {color:red}-1 release audit{color}.  The applied patch generated 5 release audit warnings.

    {color:red}-1 javac{color}.  The patch appears to cause the [build to fail|https://builds.apache.org/job/Ambari-trunk-test-patch/11389//artifact/patch-work/patchJavacWarnings.txt].

Release audit warnings: https://builds.apache.org/job/Ambari-trunk-test-patch/11389//artifact/patch-work/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11389//console

This message is automatically generated.

> Aggregate local metrics for minute aggregation time window
> ----------------------------------------------------------
>
>                 Key: AMBARI-20758
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20758
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-metrics
>    Affects Versions: 2.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20758.patch
>
>
> - Abstract Sink checks if there is local known monitor port available to write (e.g.:
61888)
> - Handshake / Ping to make sure its the monitor and is accepting writes
> - Start sending metrics only to the monitor
> - Monitor sends metrics at the global send interval (1 minute) with all the granularity
of the sink
> - Monitor aggregates first interval (5 min) data and sends it every interval seconds.
(5 min)
> - The monitor interface look the same as that of collector (http server: maybe Flask)
> - Security concerns need to be addressed as well. (https/spnego?)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message