[MDEV-11513] Database Cluster gets stopped by flowcontrol Created: 2016-12-09 Updated: 2019-05-20 Resolved: 2019-05-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.1.9 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Bastian Widmer | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | galera | ||
| Environment: |
Galera 25.3.18(r3632), Ubuntu 14.04.5 LTS, mysqld Ver 10.1.19-MariaDB-1~trusty for debian-linux-gnu on x86_64 (mariadb.org binary distribution) |
||
| Description |
|
Hi there We’re running on a galera cluster since over a year now. Until recently we didn’t see bigger issues but lately we encountered that Flow Control is stopping our clusters replication regularly. After reading and researching we did following configuration changes:
We also have a second Database Cluster setup in order to test things out but it's hard to reproduce because we don't know what exactly leads to the Flow Control issue. Our wsrep log shows following behaviour during the time when the flow control invokes the pausing The database connection is handled via maxscale. First there is the log of the master node based on maxscale where all the reads and writes end up:
And the wsrep log on the slaves during that time
What we noticed
We're trying to find out why this happens but till now we didn't find a solution. Is there a way to find out which writesets cause the IDX increase? An earlier post in the galera group something was posted which sounds like a familiar issue: Feel free to get back to me if i should provide further information. I'm happy to provide more information. |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2019-05-20 ] |
|
Can you try to reproduce with more recent version of MariaDB and Galera library. |