search

twitter-archive / mysos

Cotton (formerly known as Mysos)
https://incubator.apache.org/projects/cotton.html
588 stars 67 forks source link

Master and slave have equal Mysql server ids #24

Open puluto opened 9 years ago

puluto commented 9 years ago

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).

don't start replication.

xujyan commented 9 years ago

How did you get this error?

Mysos scheduler controls the server id that each instance uses and it's incremented each time an instance is launched to guarantee its uniqueness.

Could you elaborate on your setup?

puluto commented 9 years ago

I got eth error when used vagrant test this project，so my setup was defaults in vagrant。

benley commented 8 years ago

for anyone else who runs into this, it happens because mysql 5.6 doesn't allow slave_id 0 to be used with replication enabled. If it's set to 0 it auto-increments to 1, which collides with the second mysos task. The fix is pretty simple - just start numbering the instances at 1 instead of 0: https://github.com/benley/mysos/commit/531478e517c7810e5287a91b4bd30e364cf6736c

seadonfrank commented 6 years ago

I did face the similar issue with the same error. The solution was to correct the PublicIP while creating a salve in the "CHANGE MASTER TO MASTER_HOST" query.

The same error does appear when you use the same IP of the slave as a masterIP while creating a slave. Hence, the MySql slave server tends to point to the same server IP (Slave IP rather than the master IP) forming a conflict of same server ID