[Linux-HA] My Second Pacemaker Cluster

Dan Frincu dfrincu at streamwide.ro
Wed Oct 20 00:41:33 MDT 2010


Robinson, Eric wrote:
> I am now deploying my second MySQL+Pacemaker+DRBD cluster. To avoid
> conflicting with the first cluster on the same LAN, should I vary the
> mcastaddr, mcastport, or both? Is there anything else that I should vary
> to avoid conflicting with the first cluster? 
You need a unique network socket for each ringnumber. At least that's 
the recommendation if you want to use resource-level fencing => 

Other than that, I usually use range for mcastaddr, and to 
make them unique between multiple deployments within the same network, I 
rely on parts from the bindnetaddr to create a unique socket.

For example looking at your config, is used for ringnumber 
0 and for ringnumber 1, then the mcastaddr for ringnumber 0 
can be and for ringnumber 1, These two should 
match on all nodes that should be in the same cluster. Making different 
sockets for other clusters based on this scheme is easier this way. I 
usually don't change the port, but that's just my choice on the matter.


> The totem section on the first cluster looks like this...
> totem {
>         version:        2
>         token:          5000
>         token_retransmits_before_loss_const: 10
>         join:           1000
>         consensus:      7500
>         vsftype:        none
>         max_messages:   20
>         secauth:        off
>         threads:        0
>         clear_node_high_bit: yes
>         rrp_mode: passive
>         # nodeid:         1234
>         interface {
>                 ringnumber: 0
>                 bindnetaddr:
>                 mcastaddr:
>                 mcastport: 4000
>         }
>         interface {
>                 ringnumber: 1
>                 bindnetaddr:
>                 mcastaddr:
>                 mcastport: 4000
>         }
> }
> --
> Eric Robinson
> Disclaimer - October 19, 2010 
> This email and any files transmitted with it are confidential and intended solely for General Linux-HA mailing list. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. 
> This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

Systems Engineer
Streamwide Romania

More information about the Linux-HA mailing list