You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2014/05/28 09:02:01 UTC
[jira] [Commented] (AMBARI-5906) Add support to create arbitrary
gmond servers for metrics collection
[ https://issues.apache.org/jira/browse/AMBARI-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010857#comment-14010857 ]
Siddharth Wagle commented on AMBARI-5906:
-----------------------------------------
+1 LGTM
> Add support to create arbitrary gmond servers for metrics collection
> --------------------------------------------------------------------
>
> Key: AMBARI-5906
> URL: https://issues.apache.org/jira/browse/AMBARI-5906
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.6.1
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 1.6.1
>
> Attachments: AMBARI-5906.patch
>
>
> *Proposal*:
> Ambari ships with a fixed set of gmond servers all tied to specific service components. If user installs a custom component or a yarn application and needs a dedicated gmond server he will need to edit the Ambari Ganglia scripts.
> The proposal is to ship Ambari with a set of named gmond server instances that can be activated though reconfiguration of ganglia. This is precursor to the feature (possibly using Custom Commands) to add arbitrary named gmond servers dynamically.
> Once the gmond servers are activated, they can be used to submit ganglia metrics that will be available through Ganglia Web Server. A followup JIRA will be created to add support for accessing metrics through Ambari REST API.
> Initially, Ambari will have three named instances "Application1", "Application2", and "Application3" available.
> These can be activated through global variable "enabled_app_servers" that accepts comma separated names for application specific servers to be activated. Ganglia needs to be restarted after the configuration is modified.
--
This message was sent by Atlassian JIRA
(v6.2#6252)