[ClusterLabs] Pacemaker 1.1.15 - Release Candidate 4
The latest release candidate for Pacemaker version 1.1.15 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc4 With this release candidate, we now provide three sample alert scripts to use with the new alerts feature, installed in the /usr/share/pacemaker/alerts directory. The ./configure script has a new "--with-configdir" option. Different systems put start-up environment variables in various locations -- /etc/sysconfig, /etc/default, /etc/conf.d, and so on. We looked into auto-detecting this, but it became clear that the user (or packager) is in the best position to configure it. The default is /etc/sysconfig. Bugfixes since 1.1.15-rc3 include multiple memory issues, important fixes for ocf:pacemaker:controld, and improved compatibility with nodes running version 1.1.11 or earlier during rolling upgrades. Everyone is encouraged to download, compile and test the new release. Your feedback is important and appreciated. This is most likely very close to the final 1.1.15 release. -- Ken Gaillot ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change
Feri, Thanks for the answer - this is very useful. Ilia > On Jun 10, 2016, at 3:13 AM, Ferenc Wágner wrote: > > Ilia Sokolinski writes: > >> We have a custom Master-Slave resource running on a 3-node pcs cluster on >> CentOS 7.1 >> >> As part of what is supposed to be an NDU we do update some properties of the >> resource. >> For some reason this causes both Master and Slave instances of the resource >> to be restarted. >> >> Since restart takes a fairly long time for us, the update becomes very much >> disruptive. >> >> Is this expected? > > Yes, if you changed a parameter declared with unique="1" in your resource > agent metadata. > >> We have not seen this behavior with the previous release of pacemaker. > > I'm surprised... > -- > Feri ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command
This solved the problem. Thanks. :) On Mon, Jun 6, 2016 at 9:49 AM, Nikhil Utane wrote: > Yes, everything is (almost) latest version. Will give this a try. Thanks > Jan. > > On Fri, Jun 3, 2016 at 9:04 PM, Jan Pokorný wrote: > >> Hello Nikhil, >> >> On 03/06/16 16:33 +0530, Nikhil Utane wrote: >> > The node is up alright. >> > >> > [root@airv_cu pcs]# pcs cluster status >> > Cluster Status: >> > Stack: corosync >> > Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition WITHOUT quorum >> > Last updated: Fri Jun 3 11:01:32 2016 Last change: Fri Jun 3 >> > 09:57:52 2016 by hacluster via crmd on airv_cu >> > 2 nodes and 0 resources configured >> > >> > Upon entering command "pcs cluster standby airv_cu" getting below error. >> > Error: cannot load cluster status, xml does not conform to the schema. >> > >> > What could be wrong? >> >> if you have a decently recent versions of both pacemaker and pcs (ca 3 >> months old or newer) it's entirely possible that this commit will >> resolve it for you on the pacemaker side: >> >> >> https://github.com/ClusterLabs/pacemaker/pull/1040/commits/87a82a165ccacaf1a0c48b5e1fad684a8dd2d8c9 >> >> I'm just about to provide update to the expected test results and then >> it (the whole pull request) is expected to land soon after that. >> >> -- >> Jan (Poki) >> >> ___ >> Users mailing list: Users@clusterlabs.org >> http://clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> >> > ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change
Ilia Sokolinski writes: > We have a custom Master-Slave resource running on a 3-node pcs cluster on > CentOS 7.1 > > As part of what is supposed to be an NDU we do update some properties of the > resource. > For some reason this causes both Master and Slave instances of the resource > to be restarted. > > Since restart takes a fairly long time for us, the update becomes very much > disruptive. > > Is this expected? Yes, if you changed a parameter declared with unique="1" in your resource agent metadata. > We have not seen this behavior with the previous release of pacemaker. I'm surprised... -- Feri ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
