ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-21458) Provide ability to shard Cluster second aggregation across appId.
Date Thu, 31 Aug 2017 10:01:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmytro Sen resolved AMBARI-21458.
---------------------------------
    Resolution: Fixed

Committed to branch-3.0-ams

> Provide ability to shard Cluster second aggregation across appId.
> -----------------------------------------------------------------
>
>                 Key: AMBARI-21458
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21458
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-metrics
>    Affects Versions: 3.0.0
>            Reporter: Aravindan Vijayan
>            Assignee: Dmytro Sen
>             Fix For: 3.0.0
>
>
> This is a major pain point for AMS, where a single collector is not able to read the
entire last 2 mins data from HBase to perform aggregation. The proposal intends to solve the
problem in 2 ways.
> 1. Shard the cluster aggregator second across collector instances.
> 2. Each shard will hold 2 mins (or 1 min) data in memory and then writ aggregated data
into HBase. This will eliminate the need to read the last 2 mins data from HBase for aggregation,
in normal course of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message