Resume mysqld startup in case wsrep-recover fails
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 | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I noticed that, when mysqld is killed (ie. process group kill) during SST at
WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:
2014-10-07 18:24:11 21468 [Note] WSREP: (a73fdb95, 'tcp://
it leaves an unclean data directory behind, naturally since the streaming process is killed while it is writing.
d) Next when you start mysqld again, mysqld --wsrep-recover will fail with some indeterminate error because of corrupt data directory. Since wsrep-recover fails, we bail out here.
How to fix this
===============
As I mentioned, we failed out at wsrep-recover if the recover failed. What needs to be done is let it go to next stage, and allow mysqld/galera to decide what to do next. At this point, since grastate.dat has 00000000-
Optional:
========
Add an option to [mysqld_safe] to use older behavior but default to newer one.
affects: percona-
Related branches
- Raghavendra D Prabhu: Pending requested
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXC-1750