[MXS-307] Add multi-source replication support in MaxScale Created: 2015-08-12 Updated: 2017-12-01 Resolved: 2016-10-10 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Dipti Joshi (Inactive) | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2016-15 |
| Description |
|
Add support for multi-source replication in Binlog Server (1) Binlog Server should be able to replicate from multiple masters (2) Binlog Server should be able to re-write the schema name See example how it is done in a MariaDB/MySQL slave https://mariadb.com/blog/multisource-replication-how-resolve-schema-name-conflicts |
| Comments |
| Comment by Massimiliano Pinto (Inactive) [ 2016-08-03 ] |
|
Where will the events from from multiple backends be saved? Binlog server design is to provide exact replica of the master binlog files. Some questions: 1) There will be different binlog files, stored in different direcories, based on CHANGE MASTER 'master-name' Is this a proper use case for a replication proxy? Maybe not. Right now it's possible to configure N binlog services, even without listeners and get separate binlog events from separate servers. The mentioned "re-write the schema name" applies to SQL thread in the salve which cannot apply in binlog server where there is no SQL handling A detailed document with proper uses cases is needed before any estimate. This blog post is also important: http://blog.booking.com/better_parallel_replication_for_mysql.html It describes parallel replication and binlog servers |