[MDEV-15747] WSREP: BF lock wait long for trx Created: 2018-04-02 Updated: 2018-09-13 Resolved: 2018-09-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Storage Engine - InnoDB, Stored routines |
| Affects Version/s: | 10.1.32 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Pramudya Aditya | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 1 |
| Labels: | galera, innodb, replication | ||
| Environment: |
CentOS7, Galera, HAProxy, KeepAlived |
||
| Attachments: |
bug#1.JPG
mysql_error.log.185
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Hi, it seems the problem of WSREP: BF lock wait long for trx .... is appear again and locking a whole cluster (galera). I have a cluster with 3 nodes using HAProxy and KeepAlived. The cluster hung several times for a week. And one of the node produced a bigger error log than the others. As you can see inside attachment, the error log that i extracted before writing so many BF lock wait long for trx .... If any mistake, pls let me know. I using earlier version of MariaDB, 10.1.31 is this still buggy? or i don't figure it out that this isn't bug? Sorry for my bad english *edit : For each hung, i take a look on the error log and seems that the crash triggered by sql statement "commit". Any idea? Spec: |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2018-08-23 ] |
|
I would need full unedited error log that will also contain those BF lock wait long messages. |