You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Aravindan Vijayan (JIRA)" <ji...@apache.org> on 2016/10/04 16:48:21 UTC
[jira] [Updated] (AMBARI-17909) AMS Storm Sink: apply change of
Storm metrics improvement - worker level aggregation
[ https://issues.apache.org/jira/browse/AMBARI-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aravindan Vijayan updated AMBARI-17909:
---------------------------------------
Fix Version/s: 2.4.0
> AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-17909
> URL: https://issues.apache.org/jira/browse/AMBARI-17909
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17909-v1.patch, AMBARI-17909-v2.patch
>
>
> Abstraction:
> This issue is for following up changes on STORM-2006: Storm metrics feature improvement: support per-worker level metrics aggregation.
> Details:
> With recent patches for AMS and AMS Storm sink, AMS stores task level metrics from Storm, and relevant dashboards can be configured via Grafana.
> But we found that it incurs too many kinds of metrics and also too many data points published to AMS because even a topology can have lots of tasks.
> In order to reduce this, I addressed STORM-2006, but it also needs AMS Storm sink and relevant Storm configurations to be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)