[MXS-224] BLR: Improve disconnection reporting of connections via the MySQL interface Created: 2015-06-25 Updated: 2015-08-24 Resolved: 2015-08-24 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.0 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Simon J Mudd | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Maxscale logging shows in syslog after a disconnection from the binlog server's MySQL port: I had actually sent some SQL commands to the binlog router, so it looks odd. So the data shown are "binlog events", events and bytes. Given that a SQL connection may be used for slave streaming or configuring the BLR it might be useful to adjust the logging: Jun 25 17:34:00 xxxxx MaxScale[12049]: blr_service: Slave 1.2.3.4, server id 0, disconnected after 43 seconds. 999 SQL commands, 9999 binlog events (99999 bytes). |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-08-18 ] |
|
Massimiliano Pinto Is this fixed ? |
| Comment by Massimiliano Pinto (Inactive) [ 2015-08-19 ] |
|
Fix added to 'develop' and '1.2.1-binlog_router_trx' https://github.com/mariadb-corporation/MaxScale/commit/895989446d58e54351b593a2c11153efe13863b2 Real slave (5 SQL commands include statements sent before registration) 2015-08-19 05:37:36 Binlog_Service: Slave 127.0.0.1, server id 2, disconnected after 96 seconds. 5 SQL commands, 288 binlog events (296099 bytes) mysql client to maxscale: here only SQL commands, no events. 2015-08-19 05:35:47 Binlog_Service: Slave 127.0.0.1, server id 2, disconnected after 320 seconds. 6 SQL commands, 0 binlog events (0 bytes). |