[MXS-878] Binlogrouter logs an error when a 10.1 slave connects Created: 2016-09-29 Updated: 2017-12-01 Resolved: 2016-12-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.1.0 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Description |
|
When a 10.1 slave connects to a binlogrouter, MaxScale logs the following error:
This should not be logged as an error as it is expected. |
| Comments |
| Comment by Massimiliano Pinto (Inactive) [ 2016-09-29 ] |
|
MariaDB 10 slaves always send the request when connecting to a Master: SELECT binlog_gtid_pos('binlog.000001',4) This is sent even if MASTER_USE_GTID=no I guess we could also ask the server team whether this query could be removed from slave registration. |
| Comment by markus makela [ 2016-09-29 ] |
|
What I mean is that if MaxScale would detect that a slave does SELECT binlog_gtid_pos(...) as a part of the registration process, we could just ignore it instead of logging an error message. |
| Comment by Massimiliano Pinto (Inactive) [ 2016-09-29 ] |
|
Yes, we can do it for now. I was thinking about a future GTID support for connecting slaves. For that reason the slave should ask binlog_gtid_pos only if it's really needed. |
| Comment by markus makela [ 2016-12-05 ] |
|
The particular error message is suppressed since we know it'll be requested by 10.1 slaves. |