[MXS-1163] Log flood using binlog server on Ubuntu Yakkety Yak Created: 2017-03-04 Updated: 2017-10-09 Resolved: 2017-10-09 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | 2.0.4, 2.1.0 |
| Fix Version/s: | 2.1.10, 2.2.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | VAROQUI Stephane | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 2017-42, 2017-43 | ||||||||
| Description |
|
maxsclale log is lofin around 500M per day of such information, The only way to get read of it is to disable the binlog router 2017-03-04 13:26:45 error : Write to dcb 0x7c89b0 in state DCB_STATE_ALLOC fd 18 failed due errno 104, Connection reset by peer stretch/sid [MaxInfo] [MaxInfo JSON Listener] [Replication] [Replication Listener] [MySQL Monitor]
[Read-Only Service]
[Read-Write Service]
[MaxAdmin Service]
[Write Connection Router] [Read-Only Listener] [Write-Only Listener] [Read-Write Listener] #[MaxAdmin Listener]
[server2] [server1] |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2017-03-04 ] | |||||||||||||
|
stephane@skysql.com You are using MaxScale 2.0.4 Please try 2.1.0 beta which has a new global setting log_throttling to throttle flooding of log file | |||||||||||||
| Comment by VAROQUI Stephane [ 2017-03-04 ] | |||||||||||||
|
Thanks Dipty , I'll try this and report | |||||||||||||
| Comment by VAROQUI Stephane [ 2017-03-05 ] | |||||||||||||
|
issue still the same with MaxScale 2.1.0 Beta | |||||||||||||
| Comment by VAROQUI Stephane [ 2017-03-05 ] | |||||||||||||
|
Still can reproduce with minimum conf file [Replication] [Replication Listener] [MaxAdmin Service] [CLI Inet Listener] [server2] [server1] | |||||||||||||
| Comment by Johan Wikman [ 2017-03-06 ] | |||||||||||||
|
Those errors are logged too rarely to be throttled. By default, a message that is logged 10 times in one second will be throttled for 10 seconds. | |||||||||||||
| Comment by Marco Fretz [ 2017-05-11 ] | |||||||||||||
|
what do those errors actually mean? is there something wrong? we have several maxscale / galera installations with mariadb 10.1 on Ubuntu 16.04. We're using maxscale 2.0.5 and I see those errors on only one of our cluster setups:
Unfortunately I cannot upgrade this affected system to a beta version (2.1). any ideas? | |||||||||||||
| Comment by Marco Fretz [ 2017-05-16 ] | |||||||||||||
|
an update from my side: i tested the latest 2.1.x package I found for Xenial 16.04 and the errors are the same, looks like they are not related to connection to maxscale, possibly coming from the galera monitor? any news on this? | |||||||||||||
| Comment by Massimiliano Pinto (Inactive) [ 2017-09-27 ] | |||||||||||||
|
Is binlog server configured or there is just the entry in the config file? | |||||||||||||
| Comment by Massimiliano Pinto (Inactive) [ 2017-10-09 ] | |||||||||||||
|
The un-configured backend server is no longer checked for db users auth loading. |