By: Frederic Descamps

Frederic Descamps — Mon, 17 Feb 2014 08:42:41 +0000

Hi Alex,

During my test, if you don’t define a unique a server_id, the default value is 1 and then async replication (Slave_IO_Running) will stop with the following message :

Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).

Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).

And of course you should not start this option with “–log-slave-updates” it will even fail to avoid infinite loop.

So, for me, unique server_id is still necessary.

By: Alex

Alex — Fri, 14 Feb 2014 22:12:47 +0000

Hooray to that!

Yet, doesn’t gtid_mode=on make server_id unnecessary?

Comments on: Changing an async slave of a PXC cluster to a new Master using 5.6 and GTID

By: Frederic Descamps

By: Alex