[
https://issues.apache.org/jira/browse/AMBARI-20758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985356#comment-15985356
]
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/12865173/AMBARI-20758_4.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11502//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_4.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)
