regression test for lp:1100496 runs too slowly
Bug #1262887 reported by
Seppo Jaakola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Medium
|
Seppo Jaakola | |||
5.6 |
Fix Released
|
Undecided
|
Seppo Jaakola | |||
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
Running the regression test for lp:1100496 shows that the slave node freezes for long periods. The test will eventually pass, but just takes too long to complete.
Running same test against a native MySQL replication pair does not show similar slowness.
Changed in codership-mysql: | |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
status: | New → In Progress |
Changed in codership-mysql: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Fix was pushed into wsrep-5.5, in revision: http:// bazaar. launchpad. net/~codership/ codership- mysql/wsrep- 5.5/revision/ 3934
The problem was due to InnoDB purge thread which would not treat lock types on WSREP_BF correctly when inheriting locks.
In the fix, InnoDB lock manager was refactored to not use WSREP_BF lock mode anymore. Locking priority is implemented by checking running transactions BF state at the time of each lock conflict. We will need another round of refactoring, to not access mysql THD structure for each lock conflict, transaction state can be held in InnoDB trx.