Hello,
we're working on a two node setup to achieve high
availability using 4.1.8;
we first setup both servers with --bin-log, and only
the slave server (db1) with --log-slave-updates. (binary logfile
name is "master" on both server)
replication from db0 to db1 runs smoothly.
next, we stop both servers and db1 becomes master, with
db0 slave. Replication still ok.
second stop: db0 becomes master like at the beginning,
db1 slave.
Now the replication is broken, and we get impossible
positions like this:
050301 23:08:35 [Note] Slave SQL thread initialized,
starting replication in log 'master.000009' at position 8198468,
relay log './db0-relay-bin.000004' position: 169153
(binary log file master.000009 is shorter than this size on db0,
and master.000010 already exists)
050301 23:08:35 [ERROR] Slave I/O thread: error connecting to master
'repl@db1:3306': Error: 'Lost connection to MySQL server during query'
errno: 2013 retry-time: 60 retries: 86400
050301 23:08:39 [ERROR] Slave I/O thread killed while connecting to master
050301 23:08:39 [ERROR] Slave I/O thread exiting, read up to log
'master.000009', position 8198468
050301 23:08:39 [ERROR] Error reading relay log event: slave SQL thread
was killed
Do you know if we forgot an important option, or maybe something
is wrong in our setup ?
Regards,
Olivier Kaloudoff
CKR Solutions Open Source
Mandelieu, France
http://www.ckr-solutions.com
