[MXS-4697] Binlogrouter does not support binlog_checksum=NONE Created: 2023-08-03 Updated: 2023-11-06 |
|
| Status: | Open |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | 2.5.27, 6.4.8, 22.08.7, 23.02.2 |
| Fix Version/s: | 2.5, 6.4, 22.08, 23.02 |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | Niclas Antti |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-192 |
| Description |
|
If the server from where the binlog events are being replicated does not have binlog checksums enabled, the binlogrouter The binlogrouter should support replication without checksums but given the fact that by default replication uses checksums, the importance of supporting this is not known. For the sake of completeness, it should still be supported by the router. |
| Comments |
| Comment by markus makela [ 2023-08-03 ] |
|
For 2.5 and other older releases, the first thing to do would be to disable replication of binlogs that do not have checksums enabled. Since by default the binlog checksums are enabled and this prevents accidental corruption, this seems like a reasonable action to take in the short term. As for whether there's a real need to ever support non-checksummed binlogs remains to be seen but for the time being I'll leave this open and rename it to Binlogrouter does not support binlog_checksum=NONE. |