Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC

Restart node bootstrapped in PXC

Bug #1291024 reported by Raghavendra D Prabhu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Fix Released
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC 5.5.37-25.10
5.6
Fix Released
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC 5.6.15-25.5

Bug Description

Currently when you restart a node, in init scripts, it restarts it without --wsrep-new-cluster. Restarting with --wsrep-new-cluster may be required.

Revision history for this message
Jay Janssen (jay-janssen) wrote :

Why would you ever automatically start with --wsrep-new-cluster?

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

Need not be automatically. People use init scripts when interactively starting PXC as well (or debugging or testing or upgrading or lot of other things). Problem was that when a bootstrapped node was restarted, it could have potentially failed (if it was the only node in the cluster).

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

And it should have as there was obviously a problem with a cluster. New cluster should be started only manually, that's why wsrep-new-cluster can't be put in my.cnf.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1647

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

Other bug subscribers

Remote bug watches

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