ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17249) Storm metrics sink should include worker host and port to metric name when metrics are coming from SystemBolt
Date Thu, 30 Jun 2016 18:32:10 GMT

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

Aravindan Vijayan updated AMBARI-17249:
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0
           Status: Resolved  (was: Patch Available)

Pushed to trunk and branch-2.4

trunk
{code}
commit 3ff0ddc663c58ae044385ac18660478484ae4cb5
Author: Aravindan Vijayan <avijayan@hortonworks.com>
Date:   Thu Jun 30 11:30:23 2016 -0700

     AMBARI-17249 : Storm metrics sink should include worker host and port to metric name
when metrics are coming from SystemBolt (Jungtaek Lim via avijayan)
{code}

branch-2.4
{code}
commit 0b3fc3f1cb079d4d99590364eafa9cfd2d0b91ff
Author: Aravindan Vijayan <avijayan@hortonworks.com>
Date:   Thu Jun 30 11:14:14 2016 -0700

     AMBARI-17249 : Storm metrics sink should include worker host and port to metric name
when metrics are coming from SystemBolt (Jungtaek Lim via avijayan)
{code}

[~kabhwan] Please close the review as well. 

> Storm metrics sink should include worker host and port to metric name when metrics are
coming from SystemBolt
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17249
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17249
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Jungtaek Lim
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17249-v1.patch
>
>
> Background: SystemBolt is reserved component for each worker which exposes worker level
metrics like Memory, GC, and uptime, and so on.
> All SystemBolts have -1 as task id, so identifying SystemBolt components to task id as
same as normal components will fail.
> Since each worker is identified by (worker host, port) pair, we can add hostname and
port to metric name to make metric name unique.
> Since it's only for SystemBolt, instead of adding hostname and port to all of metrics,
we can add these to specific metrics which are coming from SystemBolt.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message