Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Pacemaker

A processor joined or left the membership and a new membership was formed.

 

 

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded


hugo.deprez at gmail

Jun 24, 2012, 5:55 AM

Post #1 of 4 (540 views)
Permalink
A processor joined or left the membership and a new membership was formed.

Hello,

I guess this as laready been raised but I do have the following
message on some of my clusters :

Jun 24 12:00:02 server corosync[27089]: [TOTEM ] A processor joined
or left the membership and a new membership was formed.
Jun 24 14:10:02 server corosync[27089]: [TOTEM ] A processor joined
or left the membership and a new membership was formed.

Don't really know why. Ressources Load and ram seems to be fine on that server.

I guess I need to take care of this message as this can lead to wrong
behaviour on the cluster.

I was wondering If I need to change the value of consensus (currently
3000) to solve this issue.

Any idea ?

Regards,

Hugo

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


andrew at beekhof

Jun 27, 2012, 7:42 PM

Post #2 of 4 (517 views)
Permalink
Re: A processor joined or left the membership and a new membership was formed. [In reply to]

On Sun, Jun 24, 2012 at 10:55 PM, Hugo Deprez <hugo.deprez [at] gmail> wrote:
> Hello,
>
> I guess this as laready been raised but I do have the following
> message on some of my clusters :
>
> Jun 24 12:00:02 server corosync[27089]:   [TOTEM ] A processor joined
> or left the membership and a new membership was formed.
> Jun 24 14:10:02 server corosync[27089]:   [TOTEM ] A processor joined
> or left the membership and a new membership was formed.
>
> Don't really know why. Ressources Load and ram seems to be fine on that server.

More than likely its a network issue of some kind.

> I guess I need to take care of this message as this can lead to wrong
> behaviour on the cluster.
>
> I was wondering If I need to change the value of  consensus (currently
> 3000) to solve this issue.

More likely either or both of these two would help more:

# How long before declaring a token lost (ms)
token: 5000

# How many token retransmits before forming a new configuration
token_retransmits_before_loss_const: 10

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


hugo.deprez at gmail

Jul 1, 2012, 2:09 AM

Post #3 of 4 (500 views)
Permalink
Re: A processor joined or left the membership and a new membership was formed. [In reply to]

Thank you for the information I'll change the configuration and see
what will happen.
Hard to troubleshoot network issue.
I didn't detect any packets losts.

Running cluster on VM seems a bit tricky.

On 28 June 2012 04:42, Andrew Beekhof <andrew [at] beekhof> wrote:
> On Sun, Jun 24, 2012 at 10:55 PM, Hugo Deprez <hugo.deprez [at] gmail> wrote:
>> Hello,
>>
>> I guess this as laready been raised but I do have the following
>> message on some of my clusters :
>>
>> Jun 24 12:00:02 server corosync[27089]: [TOTEM ] A processor joined
>> or left the membership and a new membership was formed.
>> Jun 24 14:10:02 server corosync[27089]: [TOTEM ] A processor joined
>> or left the membership and a new membership was formed.
>>
>> Don't really know why. Ressources Load and ram seems to be fine on that server.
>
> More than likely its a network issue of some kind.
>
>> I guess I need to take care of this message as this can lead to wrong
>> behaviour on the cluster.
>>
>> I was wondering If I need to change the value of consensus (currently
>> 3000) to solve this issue.
>
> More likely either or both of these two would help more:
>
> # How long before declaring a token lost (ms)
> token: 5000
>
> # How many token retransmits before forming a new configuration
> token_retransmits_before_loss_const: 10
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
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


andrew at beekhof

Jul 1, 2012, 2:20 PM

Post #4 of 4 (503 views)
Permalink
Re: A processor joined or left the membership and a new membership was formed. [In reply to]

On Sun, Jul 1, 2012 at 7:09 PM, Hugo Deprez <hugo.deprez [at] gmail> wrote:
> Thank you for the information I'll change the configuration and see
> what will happen.
> Hard to troubleshoot network issue.
> I didn't detect any packets losts.
>
> Running cluster on VM seems a bit tricky.

What might be happening is that the OS is pausing the VM(s), albeit
very briefly.
That might be enough to make it look like there were network hiccups.

http://bugzilla.redhat.com/show_bug.cgi?id=820821 has some related discussion.

>
> On 28 June 2012 04:42, Andrew Beekhof <andrew [at] beekhof> wrote:
>> On Sun, Jun 24, 2012 at 10:55 PM, Hugo Deprez <hugo.deprez [at] gmail> wrote:
>>> Hello,
>>>
>>> I guess this as laready been raised but I do have the following
>>> message on some of my clusters :
>>>
>>> Jun 24 12:00:02 server corosync[27089]: [TOTEM ] A processor joined
>>> or left the membership and a new membership was formed.
>>> Jun 24 14:10:02 server corosync[27089]: [TOTEM ] A processor joined
>>> or left the membership and a new membership was formed.
>>>
>>> Don't really know why. Ressources Load and ram seems to be fine on that server.
>>
>> More than likely its a network issue of some kind.
>>
>>> I guess I need to take care of this message as this can lead to wrong
>>> behaviour on the cluster.
>>>
>>> I was wondering If I need to change the value of consensus (currently
>>> 3000) to solve this issue.
>>
>> More likely either or both of these two would help more:
>>
>> # How long before declaring a token lost (ms)
>> token: 5000
>>
>> # How many token retransmits before forming a new configuration
>> token_retransmits_before_loss_const: 10
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker [at] oss
>> 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
> 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
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

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.