Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5.17, 6.2.0
-
None
Description
The OK byte at offset 4 was not set by the binlogrouter and instead the byte at offset 5 was always set to 0. This caused at least the binlogfilter to error out when it found garbage where it expected the 0x0 OK byte to exits.
Attachments
Issue Links
- is duplicated by
-
MXS-4342 Binlog router causing database slowness
- Closed