Bug #79796 Making Multi source replication better
Submitted: 29 Dec 2015 8:38
Reporter: Ankit T Email Updates:
Status: Open Impact on me:
Category:MySQL Server Severity:S4 (Feature request)
Version:5.7.9 community edition OS:Any
Assigned to: CPU Architecture:Any
Tags: Multi Source Replication: Binary logging for mysql.slave_relay_log_info table

[29 Dec 2015 8:38] Ankit T
We have MySQL 5.7 community edition replica which is replicating data from multiple sources, the replication is working in traditional coordinate system i.e. NOT GTID, with the masters on 5.6 community version. 

We plan to a set of replicas below this MySQL 5.7 multi source replica but problem with this is if the 5.7, which is acting as master to 5.7 slaves, goes down then we cannot put the rearrange the topology to get one of its slave to take up its role as the server which is replicating from multiple sources since we will not have the replication coordinates of each upstream source. This source replication coordinate info on the Multi Source 5.7 is stored in mysql.slave_relay_log_info table and I checked the DML activity done by replication thread in this Innodb table is not logged into binary logs for obvious reasons - this information holds server specific replication information. 

So I am requesting a feature which will replicate the data in this table to some other table which will allow us to use this information and rearrange the replication topology.

How to repeat:

Suggested fix:
An implicit replication filter which would log the DML on mysql.slave_relay_log_info table into binary log and will replicate into some other table so that one can get this info without interfering with normal replication process.