On 29 Oct 2013, at 12:39 am, Karl Rößmann <k.roessm...@fkf.mpg.de> wrote:
> > Hi, > we want to increase some corosync token-parameters slightly: > > token, > token_retransmits_before_loss_const, > consensus. > > > Is this possible Without interrupting services and resources? in this order: > > move all resources to node A i assume this should be B above > shutdown corosync/pacemaker on node A > change corosync.conf on Node A > start corosync/pacemaker on Node A > > move all resources to node B and A above here > shutdown corosync/pacemaker on node B > change corosync.conf on Node B > start corosync/pacemaker on Node B you'll still have service interruption though, since they'll be stopped when we move them to the other nodes. you could use maintenance-mode though: http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_disconnect_and_reattach.html > > > Karl Rößmann > -- > Karl Rößmann Tel. +49-711-689-1657 > Max-Planck-Institut FKF Fax. +49-711-689-1632 > Postfach 800 665 > 70506 Stuttgart email k.roessm...@fkf.mpg.de > > > > _______________________________________________ > 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