You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/04/01 17:51:32 UTC

[jira] [Resolved] (AMBARI-5245) gmond.master.conf files are generated by Ganglia Server

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

Dmitry Lysnichenko resolved AMBARI-5245.
----------------------------------------

    Resolution: Fixed

committed to trunk

> gmond.master.conf files are generated by Ganglia Server
> -------------------------------------------------------
>
>                 Key: AMBARI-5245
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5245
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.5.1
>
>
> gmond.master.conf files are generated by ganglia server scripts, but are used by ganglia monitor. In some scenarios (when "restart Ganglia service" action is performed, and gmond is restarted before gmetad), changes of gmond.master.conf have no effect on gmond until next restart. The solution is to move all code that generates gmond.master.conf files from ganglia server to ganglia monitor scripts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)