[jira] [Commented] (AMBARI-3347) Performance issue requesting metrics when dynamic metric name specified.

["Tom Beerbower (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778681#comment-13778681 ] 

Tom Beerbower commented on AMBARI-3347:
---------------------------------------

+1 on the patch.
                
> Performance issue requesting metrics when dynamic metric name specified.
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-3347
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3347
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.4.1
>            Reporter: Oleksandr Diachenko
>            Assignee: Oleksandr Diachenko
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3347.patch
>
>
> When requesting metrics like ...
> {code}
> metrics/yarn/Queue/root/default/AvailableMB
> {code}
> ... a request is generated to pull the metrics from the rrd files produced by Ganglia.  Currently the above request will result in the GangliaPropertyProvider making the following request to rrd.py for the metrics ...
> {code}
> /cgi-bin/rrd.py?c=HDPResourceManager&h=hostname
> {code}
> Note that this request does not ask for a specific metric like ...
> {code}
> m=yarn.QueueMetrics.Queue=root.default.AvailableMB
> {code}
> ... which means that *all* of the metrics are returned.  This is obviously not ideal.
> Request to rrd should include a set of regular expressions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira