You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2014/04/11 19:32:16 UTC

[jira] [Commented] (AMBARI-5445) When new host components are created thru API, some indication should be given that Nagios has to be restarted

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

Sumit Mohanty commented on AMBARI-5445:
---------------------------------------

With some input from [~mahadev] how about a more generic solution:
* Introduce the concept of a "monitoring" service
** Nagios and Ganglia are two such services
* A monitoring service, by definition, needs to be restarted when host components are added/removed
** Restart is indicated by setting a flag (if we can user stale_config = true that will be great) on all service host components
* The indicator itself is reset when a host component starts

[~dsen], can you check if the above steps fit and provide a detailed proposal

> When new host components are created thru API, some indication should be given that Nagios has to be restarted
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-5445
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5445
>             Project: Ambari
>          Issue Type: Improvement
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 1.6.0
>
>
> Need to fix this on API side



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