[Pacemaker] 1.1.8 not compatible with 1.1.7?

Fri May 10 02:36:57 EDT 2013

On 5/10/2013 1:57 AM, Andrew Beekhof wrote:
> 
> On 10/05/2013, at 6:05 AM, Rainer Brestan <rainer.brestan at gmx.net> wrote:
> 
>> Hi Andrew,
>> yes, this clarifies a lot.
>> Seems that it is really time to throw away the plugin.
>> The CMAN solution wont be able (at least from the documentation) to attach new nodes without reconfiguration and restart CMAN on the existing nodes
> 
> That doesn't sound right to me.
> CC'ing Fabio who should know more (or who does)
> 

In cman you can add and remove nodes without restarting. You need to
change the configuration tho.

short version to add a node:

- edit cluster.conf to add the node (remember to bump config_version)
- either copy it across all nodes (including the new one)
  or use ccs_sync/ricci
- issue cman_tool version -r (-S if you did copy manually) to reload
  configuration without restart
- start cman on new node

short version to remove a node:

- stop cman on the node
- edit cluster.conf to drop the node
- propagate cluster.conf
- cman_tool version -r

note that if you are moving from 2 to 3+ node or from 3+ to 2 node, you
_must_ stop the cluster first. This is because some internal corosync
defaults are different and cannot be changed at runtime yet.

Also, when removing nodes, you have to ensure that you do not remove too
many nodes at the same time or you can lose quorum.

Fabio

>> .
>> The alternative is corosync 2.x.
> 
> Not on RHEL6 - unless you're building things yourself of course.
> 
>> ClusterLabs has a quite long list of corosync versions from branch 2.0, 2.1, 2.2 und 2.3.
>> Beside the current reported issue of version 2.3, which version does ClusterLabs use for its regression test.
>> I found somewhere a note for 2.1.x, is this true ?
> 
> According to rpm, I've been using:
> 
>  Source RPM  : corosync-2.3.0-1.1.2c22.el7.src.rpm
> and
>  Source RPM  : corosync-2.3.0-1.fc18.src.rpm
> 
> 
> 
>> Rainer
>>  
>> Gesendet: Donnerstag, 09. Mai 2013 um 04:31 Uhr
>> Von: "Andrew Beekhof" <andrew at beekhof.net>
>> An: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
>> Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
>>
>> On 08/05/2013, at 4:53 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
>>
>>>
>>> On 08/05/2013, at 4:08 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
>>>
>>>>
>>>> On 03/05/2013, at 8:46 PM, Rainer Brestan <rainer.brestan at gmx.net> wrote:
>>>>
>>>>> Now i have all the logs for some combinations.
>>>>>
>>>>> Corosync: 1.4.1-7 for all the tests on all nodes
>>>>> Base is always fresh installation of each node with all packages equal except pacemaker version.
>>>>> int2node1 node id: 1743917066
>>>>> int2node2 node id: 1777471498
>>>>>
>>>>> In each ZIP file log from both nodes and the status output of crm_mon and cibadmin -Q is included.
>>>>>
>>>>> 1.) 1.1.8-4 attaches to running 1.1.7-6 cluster
>>>>> https://www.dropbox.com/s/06oyrle4ny47uv9/attach_1.1.8-4_to_1.1.7-6.zip
>>>>> Result: join outstanding
>>>>>
>>>>> 2.) 1.1.9-2 attaches to running 1.1.7-6 cluster
>>>>> https://www.dropbox.com/s/fv5kcm2yb5jz56z/attach_1.1.9-2_to_1.1.7-6.zip
>>>>> Result: join outstanding
>>>>
>>>> Neither side is seeing anything from the other, which is very unexpected.
>>>> I notice you're using the plugin... which acts as a message router.
>>>>
>>>> So I suspect something in there has changed (though I'm at a loss to say what) and that cman based clusters are unaffected.
>>>
>>> Confirmed, cman clusters are unaffected.
>>> I'm yet to work out what changed in the plugin.
>>
>> I worked it out...
>>
>> The Red Hat changelog for 1.1.8-2 originally contained
>>
>> +- Cman is the only supported membership & quorum provider, do not ship the corosync plugin
>>
>> When this decision was reversed (when I realised no-one was seeing the ERROR logs indicating it was going away), I neglected to re-instate the following distro specific patch (which avoided conflicts between the ID used by CMAN and Pacemaker):
>>
>> diff --git a/configure.ac b/configure.ac
>> index a3784d5..dafa9e2 100644
>> --- a/configure.ac
>> +++ b/configure.ac
>> @@ -1133,7 +1133,7 @@ AC_MSG_CHECKING(for native corosync)
>> COROSYNC_LIBS=""
>> CS_USES_LIBQB=0
>>
>> -PCMK_SERVICE_ID=9
>> +PCMK_SERVICE_ID=10
>> LCRSODIR="$libdir"
>>
>> if test $SUPPORT_CS = no; then
>>
>>
>> So Pacemaker < 6.4 is talking on slot 10, while Pacemaker == 6.4 is using slot 9.
>> This is why the two versions cannot see each other :-(
>> I'm very sorry.
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at 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 at 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
> 