On 11/25/11 20:31, Lars Ellenberg wrote: > On Fri, Nov 25, 2011 at 01:54:33PM +0100, Florian Haas wrote: >> On 11/25/11 13:29, Lars Ellenberg wrote: >>>> From the log snippet it's >>>> not entirely clear whether that's a recurring monitor (interval == >>>> whatever you configured, or 20 if default), or a probe (interval == 0). >>>> >>>> A recurring monitor clearly should not happen at all when unmanaged. >>> >>> That is incorrect. >>> >>> is-managed=false does still monitor the resource. It only prevents >>> pacemaker from sending start/stop etc commands to that resource. >> >> My understanding was that only probes would still occur (on >> cluster-recheck-interval, or when new nodes joined the cluster). And I >> maintain that that would be the intuitively "correct" behavior for >> unmanaged resources. Andrew? > > Well, your understanding or intuition seem to misguide you this time. > But if you think I make shit up ;-) > http://www.gossamer-threads.com/lists/linuxha/pacemaker/70606#70606
I didn't at all mean to insinuate you're making stuff up, but I still believe that the currently implemented behavior is counterintuitive and violates POLA. This difference between maintenance mode and is-managed=false simply isn't evident from crm_mon, and thus it's natural to assume that both will behave identically. Nowhere does crm_mon say "maintenance mode". The only visible difference for the user is that all resources go unmanaged. When you set is-managed=false on one resource, then that one resource goes unmanaged. What would you interpolate from that, if you were a novice? Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
