[MXS-1266] Binlog cache hierarchy for MariaDB GTID replication Created: 2017-05-16  Updated: 2017-12-01  Resolved: 2017-06-14

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 2.2.0
Fix Version/s: 2.2.0

Type: New Feature Priority: Major
Reporter: Massimiliano Pinto (Inactive) Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2017-34, 2017-35

 Description   

Enable a binlog cache hierarchy with replication domain, server_id and filename in order to fully replicate from MariaDB 10 Master(s) using GTID.

This will eliminate the need of issuing FLUSH LOGS or RESET MASTER TO in the new master.



 Comments   
Comment by Massimiliano Pinto (Inactive) [ 2017-06-06 ]

Added binlog_structure=tree | flat option.

This allows storing binlog files in tree mode:

domain_id/server_id/file_name as thet come from master FAKE_ROTATE event at registration time.

With this new option the Slave replicates with GTID mode even if the new master has changed binlog filename or sequence.
With "flat" option value the new master should have next in sequence filename (with same prefix)

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