mysqld can't handle wsrep error on exceeding max writeset size

[Alex Yurchenko]

Apparently mysqld is not prepared to handle exceeding writeset size error. See discussion at https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1269842/comments/9

This requires a better instrumentation in Galera to be able to test that at more reasonable sizes: https://bugs.launchpad.net/galera/3.x/+bug/1270921

[Raghavendra D Prabhu (raghavendra-prabhu)]

How is the fix of https://bugs.launchpad.net/codership-mysql/+bug/1280557 related to this? Does it fix it to some extent by adding error handling for it?

[Yan Zhang (yan.zhang)]

fixed in http://bazaar.launchpad.net/~codership/codership-mysql/wsrep-5.5/revision/3970

[Yan Zhang (yan.zhang)]

fixed in http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4068

[Przemek (pmalkowski)]

We've had an issue in affected PXC version (5.5.34) where after transaction size limit was reached, node has stalled and became unusable. In error log we could see lot of:
WSREP: BF lock wait long
and InnoDB monitors printed all over again. Even graceful shutdown failed to complete - mysqld kept printing InnoDB status and "WSREP: BF lock wait long" until forcibly killed.

[Yan Zhang (yan.zhang)]

Could you bug be reproducible on 5.5.37 ?

[Shahriyar Rzayev (rzayev-sehriyar)]

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