So, should I apply the patch or not? I have my own work-around in place for the spinning issue (moving set name check prior to node check). I'm seeing where I need to have more functionality in the notify function, and fewer calls to crm_master elsewhere.
I've been using the mgt GUI to create the resource definitions and start/stop the resources. Is there any more detailed information on specifically what the various options do (i.e. start, stop, cleanup resource, work as default), and how their effects differ when a resource, node, constraint, etc, is selected? The GuiGuide page on the web site contains only basic information, and the window snapshots don't match the current GUI. Thanks, Doug On Thu, 2007-04-05 at 07:40 -0600, Alan Robertson wrote: > Lars Marowsky-Bree wrote: > > On 2007-04-03T22:05:24, Alan Robertson <[EMAIL PROTECTED]> wrote: > > > >>> Yes. I'd avoid needless calls to it though as every call triggers a > >>> transition - so don't just call it in _every_ monitor operation ;-) > >> That's a good point. Unfortunately that means the RA has to keep state > >> somewhere, which is a bit of a pain. > > > > That is why I'd suggest to only call it in start or post-notify; calling > > it in post-notify basically implies it'll be called after every state > > change. > > But, for DRBD for example, the ability to become master can change > without a heartbeat state change. > > This is not at all surprising, nor is it probably uncommon. >
_______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
