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/05/18 10:50:04 UTC
[jira] [Resolved] (AMBARI-20758) Aggregate local metrics for minute
aggregation time window
[ https://issues.apache.org/jira/browse/AMBARI-20758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen resolved AMBARI-20758.
---------------------------------
Resolution: Fixed
Committed additional patch to trunk.
Rat check really failed for commands:
{code}
cd ambari-metrics/
mvn -B -nsu -DskipTests package install -Dbuild-rpm
{code}
> 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_7.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)