> On 27 Oct 2014, at 2:30 pm, Andrei Borzenkov <arvidj...@gmail.com> wrote: > > В Mon, 27 Oct 2014 11:09:08 +1100 > Andrew Beekhof <and...@beekhof.net> пишет: > >> >>> On 25 Oct 2014, at 12:38 am, Andrei Borzenkov <arvidj...@gmail.com> wrote: >>> >>> On Fri, Oct 24, 2014 at 9:17 AM, Andrew Beekhof <and...@beekhof.net> wrote: >>>> >>>>> On 16 Oct 2014, at 9:31 pm, Andrei Borzenkov <arvidj...@gmail.com> wrote: >>>>> >>>>> The primary goal is to transparently update software in cluster. I >>>>> just did HA suite update using simple RPM and observed that RPM >>>>> attempts to restart stack (rcopenais try-restart). So >>>>> >>>>> a) if it worked, it would mean resources had been migrated from this >>>>> node - interruption >>>>> >>>>> b) it did not work - apparently new versions of installed utils were >>>>> incompatible with running pacemaker so request to shutdown crm fails >>>>> and openais hung forever. >>>>> >>>>> The usual workflow with one cluster products I worked before was - >>>>> stop cluster processes without stopping resources; update; restart >>>>> cluster processes. They would detect that resources are started and >>>>> return to the same state as before stopping. Is something like this >>>>> possible with pacemaker? >>>> >>>> absolutely. this should be of some help: >>>> >>>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_disconnect_and_reattach.html >>>> >>> >>> Did not work. It ended up moving master to another node and leaving >>> slave on original node stopped after that. >> >> When you stopped the cluster or when you started it after an upgrade? > > When I started it > > crm_attribute -t crm_config -n is-managed-default -v false > rcopenais stop on both nodes > rcopenais start on both node; wait for them to stabilize > crm_attribute -t crm_config -n is-managed-default -v true > > It stopped running master/slave, moved master and left slave stopped.
What did crm_mon say before you set is-managed-default back to true? Did the resource agent properly detect it as running in the master state? Did the resource agent properly (re)set a preference for being promoted during the initial monitor operation? Pacemaker can do it, but it is dependant on the resources behaving correctly. > >> >>> I have crm_report if this >>> is not expected ... >>> >>> pacemaker Version: 1.1.11-3ca8c3b >>> >>> _______________________________________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org