Crash when setting wsrep_cluster_address to multiple addresses

Bug #1099684 reported by Robert Navarro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
New
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
New
Undecided
Unassigned

Bug Description

This is my first bug report, so bear with me!

So I have the following setting on one of my nodes (10.181.131.60)

wsrep_cluster_address = gcomm://10.181.131.60:4567,10.181.139.47:4567,10.181.131.50:4567

but the node fails to start when it references itself in the gcomm line. I'm using puppet for my configuration management and it would be nice to have all of the servers listed in the gcomm array.

When the gcomm array is self referencing the percona server instance crashes with the attached log

If I remove the self reference, the server starts up just fine and joins the cluster with no issue.

Am I not using the wsrep_cluster_address variable properly?

Revision history for this message
Robert Navarro (crshman) wrote :
affects: percona-server → percona-xtradb-cluster
Revision history for this message
Robert Navarro (crshman) wrote :

This got moved, but it looks like this is a duplicate for another bug already open: 1099413

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.