Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5.27, 6.4.8, 22.08.7, 23.02.2
-
None
Description
If a large transaction causes a binlog file larger than 4GiB to be generated, the binlogrouter will end up writing a corrupted binlog file.
Attachments
Issue Links
- relates to
-
MXS-4677 MaxScale BinlogRouter skips large transactions causing data Inconsistency on attached slave
- Closed