[MXS-4803] Binlog encryption broken Created: 2023-10-09  Updated: 2023-11-05  Resolved: 2023-11-02

Status: Closed
Project: MariaDB MaxScale
Component/s: pinloki
Affects Version/s: None
Fix Version/s: 22.08.10, 23.02.6, 23.08.3

Type: Bug Priority: Major
Reporter: Johan Wikman Assignee: Niclas Antti
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-192, MXS-SPRINT-193

 Description   

The error is rather subtle it has these effects:

  • New replicas would not be able to connect with a gtid in the past.
  • On a maxscale restart, replicas already in sync, would appear not to connect until the next update from the primary, but would otherwise function correctly.
  • A maxscale crash leaving an incomplete transaction in the binlog file being written, would allow the writer to append new transactions on top of that trx, breaking replication.

Generated at Thu Feb 08 04:31:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.