On 2011-10-13 09:19, [email protected] wrote: > Hi Florian, > > in fact, I saw an email on this ML a few weeks ago from one of you writing > that is-managed=false does not avoid monitoring, only start/stop. > And then, I checked in my on paper doc : Pacemaker 1.0.5 28 sept 2009 > (quite > old I admit !) and page 16 I saw : > is-managed TRUE Is the cluster allowed to start and stop the > resource ? > So it seemed to me that it confirms that monitoring was always allowed...
I think that interpretation is wrong. Have you tried? I mean, have you created, say, an IPaddr2 resource, enabled monitoring, then set is-managed=false, and then watched the logs for any monitor operations being invoked? > I don't understand "does probes" ... what's the meaning with regard to > "monitoring" ? A probe is the same as a monitor operation, except that it is not recurring. From time to time, such as when initiated by the administrator, when a new node joins the cluster, or when a new resource is added to the configuration, Pacemaker initiates just one run of the "monitor" action in the the RA, just to see whether the resource is currently active on a node. That single, non-recurring monitor invocation is commonly known as a probe. Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
