wsrep_recover processing conflicts with native replication threads

Bug #1132974 reported by Seppo Jaakola on 2013-02-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Low
Seppo Jaakola
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Undecided
Unassigned

Bug Description

When running wsrep recovery, mysql replication threads should not be started.

More detailed description here: https://mariadb.atlassian.net/browse/MDEV-4179

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.29-23.7.3
Seppo Jaakola (seppo-jaakola) wrote :

Moved wsrep recovery to happen before mysql slave threads are started.
Fix pushed in: http://bazaar.launchpad.net/~codership/codership-mysql/5.5-23/revision/3850

Changed in codership-mysql:
status: In Progress → Fix Committed
Changed in codership-mysql:
status: Fix Committed → Fix Released
Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-23.7.4
status: New → Fix Released

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

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

Other bug subscribers