wsrep hton refactoring
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Medium
|
Teemu Ollakka | |||
5.6 |
Fix Released
|
Medium
|
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
This ticket is used to track wsrep hton refactoring efforts which are not directly related to certain bugs.
Analysis of several bugs has indicated that wsrep hton and state code is overly complicated and easily leads to situations which are extremely hard to diagnose and debug. Some of the recent observations:
1) Transaction cleanup is done in wsrep_cleanup_
2) Cleanup and state reset after transaction finishes is incomplete and inconsistent. Some of the variables retain their non default values over transaction boundaries which may generate situations where after-crash diagnosis is impossible without extensive debug logs due to uncertainty of the state.
3) Insufficient amount of debug time sanity checks.
Some of the recent bugs that are directly or indirectly related to issues described above:
https:/
https:/
https:/
Merged to lp:codership-mysql/5.5 in http:// bazaar. launchpad. net/~codership/ codership- mysql/wsrep- 5.5/revision/ 3900