I can't find or think of a solution when ever i encounter db replication errors on affected source and repositioning the GTID in the replica. What i do is retrieve from (four) masters gtid postion (show master status) then copy it to the replica server. In replica server. set global gtid_slave_pos="1-10-1111111,2-20-2222222,3-30-3333333,4-40-444444" Is there a way to reposition the gtid_slave_posonly the affected source and will not cause any sync issues on other source that has no errors. I'm using MariaDB 10.5 for master and replica.

Upon searching for this, the main cause of this error is usually when using snapshots or cloning the machine. But I did not do this. I perform mysqldump --master-data=2 on the master then restore the dump on my slave server. Then start the slave on the position indicated on the outfile. Any idea on what caused this? I am running a multi-source replica and this error is from just 1 source. here is the complete error: >Got fatal error 1236 FROM MASTER WHEN reading DATA FROM BINARY LOG: 'A slave with the same server_uuid/server_id as this slave has connected to the master; the first event 'VM1-bin.000006' at 641809774, the last event read from '/binlogdata/VM1-bin.000009' at 146836375, the last byte read from '/binlogdata/VM1-bin.000009' at 146836375.';

I'm trying to set up multi-source replication. But, when I try and import the second database I get the error: ERROR 3079 (HY000) at line 28: Multiple channels exist on the slave. Please provide channel name as an argument. How can I supply the channel name to mysqldump I run the command: mysqldump -h1.2.3.4 -P3306 -umysqldumpuser -ppassword --dump-slave --apply-slave-statements --include-master-host-port --single-transaction --databases db_name -E -R -q -c --max_allowed_packet=2G | mysql -S/var/run/mysqld/mysqld.sock -umysqldumpuser -ppassword The first dump is fine, as I can then run: RESET SLAVE ALL FOR CHANNEL ""; CHANGE MASTER TO . . . FOR CHANNEL '; So it is now replicating over a channel. But I can't dump the second one as it gives me the above error. The only way I can see this working, would be to dump the first one, stop replication, make a note of the logfile and pos, and then wipe the slave connection, leaving replication to the first database off while I dump the second one. Only then can I start replication to both databases at the same time. This is highly impractical, especially if you are looking to combine connections from numerous locations. I have searched the documents, but can't find any reference to using mysqldump and channels.

I have n number of databases and I have to collect data from those into one database. The databases has some specific value (e.g. currencies) which I want to update from the collector database(of course I want this to update for all databases). So in the first case I need to avoid primary key collision because i don't want to loose data. I think that setting up auto_increment.increment and auto_increment.offset, can do the trick, but in the second case i have to identify specific rows in all databases. What kind of technology and topology can I use?