Hi OK thanks, but sorry it was not quite the response I was expected as I already know all that about cleanup, reprobe, etc. So more clearly my question was : Is there a way by crm to invalidate the monitoring temorarily for one specific resource ?
Thanks Alain > Hi, > > On Mon, 25 Mar 2013 16:25:54 +0100 Moullé Alain <[email protected]> wrote: >> I've tested two things : >> >> 1/ if we set maintenance-mode=true : >> >> all the configured ressources become 'unmanaged' , as displayed >> with crm_mon >> ok start stop are no more accepted >> and it seems that ressources are no more monitored any more by >> pacemaker > Probably maintainance-mode also tells the cluster-manager to completely > stop monitoring. > >> 2/ if we target only one resource via the crm resource umanage >> <resname> : >> >> it is also displayed unmanage with crm_mon >> ok start stop are no more accepted >> BUT pacemaker always monitors the resource >> >> Is there a reason for this difference ? > Its un-managed, not un-monitored ;-) > Actually this is not a problem, it will monitor as long as the service > is up. As the first monitor-action fails, the resource is marked as > "failed" and no more monitor action is run. Until you explicitely ask > for it with "cleanup <resource>" or "reprobe <node>". > > Have fun, > > Arnold > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
