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

Bug #1270920 reported by Alex Yurchenko on 2014-01-20
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Undecided
Yan Zhang
5.6
Undecided
Yan Zhang
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

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

description: updated

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?

Przemek (pmalkowski) wrote :

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) wrote :

Could you bug be reproducible on 5.5.37 ?

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers