ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-20758) Aggregate local metrics for minute aggregation time window
Date Wed, 17 May 2017 16:09:04 GMT


Hadoop QA commented on AMBARI-20758:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  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 13 new or modified
test files.

    {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-logsearch/ambari-logsearch-logfeeder
ambari-metrics/ambari-metrics-common ambari-metrics/ambari-metrics-flume-sink ambari-metrics/ambari-metrics-hadoop-sink
ambari-metrics/ambari-metrics-host-aggregator ambari-metrics/ambari-metrics-kafka-sink ambari-metrics/ambari-metrics-storm-sink
ambari-metrics/ambari-metrics-storm-sink-legacy ambari-metrics/ambari-metrics-timelineservice

Console output:

This message is automatically generated.

> Aggregate local metrics for minute aggregation time window
> ----------------------------------------------------------
>                 Key: AMBARI-20758
>                 URL:
>             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.:
> - 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

View raw message