pc.checksum is enabled by default
Bug #1229107 reported by
Alex Yurchenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Galera | Status tracked in 3.x | |||||
2.x |
Fix Released
|
Medium
|
Alex Yurchenko | |||
3.x |
Fix Released
|
Medium
|
Alex Yurchenko | |||
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
The purpose of this option is to help with debugging, and it does not seem that it ever came to rescue in real life - and probably never will provided there are no bugs in that department that it can help to detect. Even thought the overhead must be insignificant, it is probably best to disable it.
For real protection from corruption we have CRC32 on network packets, and if that fails - 128-bit hashsum for the writesets (latter is 3.x only)
Related branches
lp://staging/galera
Ready for review
for merging
into
lp://staging/~dbpercona/galera/Bug1348714
- David Bennett: Pending requested
- Diff: 0 lines
To post a comment you must log in.
Fix pushed in bazaar. launchpad. net/~codership/ galera/ 23.2.x/ revision/ 160 bazaar. launchpad. net/~codership/ galera/ 2.x/revision/ 161 bazaar. launchpad. net/~codership/ galera/ 3.x/revision/ 162
http://
http://
http://