sync level violation with wsrep checkpointing
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
High
|
Teemu Ollakka | |||
5.6 |
Fix Released
|
High
|
Teemu Ollakka | |||
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
After turning UNIV_SYNC_DEBUG on, node that was started from clean state crashed immediately at startup with:
InnoDB: sync levels should be > 290 but a level is 290
-------------
RW-LATCH INFO
RW-LATCH: 0x7fdbcbd411b0
Locked: thread 140582617687872 file /home/teemu/
Locked: thread 140582617687872 file /home/teemu/
InnoDB: sync_thread_
2013-11-07 12:38:51 7fdbf0fd2740 InnoDB: Assertion failure in thread 140582617687872 in file sync0sync.cc line 1171
The reason is calling trx_sysf_get() twice in succession, first from trx_sys_
Similar crash happens when binlog is enabled and trx_sys_
Fixes pushed: bazaar. launchpad. net/~codership/ codership- mysql/5. 5-23/revision/ 3941 bazaar. launchpad. net/~codership/ codership- mysql/wsrep- 5.5/revision/ 3923 bazaar. launchpad. net/~codership/ codership- mysql/5. 6/revision/ 4014
5.5-23: http://
5.5: http://
5.6: http://