From: Artem Koltsov Date: January 19 2005 5:18pm Subject: RE: problem after switching master / slave roles twice List-Archive: http://lists.mysql.com/replication/15 Message-Id: <1EA23548B834AB4E85CFCBB2C8EBA8880D0C44@SD-MAIL4.wfinet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Did you change master_log_pos and master_log_file values on db1 before st= ep 3? > -----Original Message----- > From: olivier kaloudoff [mailto:olivier.kaloudoff@stripped] > Sent: Wednesday, January 19, 2005 11:41 AM > To: replication@stripped > Subject: problem after switching master / slave roles twice >=20 >=20 > Hello, >=20 >=20 > I just setup a simple master / slave scheme using 4.1.8, to > achive high availability. >=20 > Now I have to test if replication is ok when I switch the > roles of my two servers, db0 and db1; >=20 > 1. starting with: db0 master, db1 slave, replication goes fine > 2. switching to: db0 slave, db1 master, data put on db1=20 > replicates fine >=20 > 3. now, switching back to: db0 master, db1 slave, the replication is > broken, and "show slave status" gives; >=20 > "Error 'Can't create database 'jmax'; database exists' on query. > Default database: 'jmax'. Query: 'create > database `jmax`" >=20 > (the jmax database has been created at step 1, replicated fine, and > now breaks for an unknown reason). >=20 >=20 > as the replication FAQ says, I used the --log-bin option on > both servers, but no --log-slave-updates option. On both servers, I > can see relay and binary logs beeing written. >=20 > did I miss something obvious, or is there a bug somewhere ? >=20 >=20 > Best Regards, >=20 >=20 > Olivier Kaloudoff > CKR Solutions Open Source > Mandelieu, France > http://www.ckr-solutions.com >=20 > --=20 > MySQL Replication Mailing List > For list archives: http://lists.mysql.com/replication > To unsubscribe: =20 http://lists.mysql.com/replication?unsub=3Dartem.koltsov@stripped =A0 Attention: Any views expressed in this message are those of the individual sender, e= xcept where the message states otherwise and the sender is authorized to = state them to be the views of any such entity. The information contained = in this message and or attachments is intended only for the person or ent= ity to which it is addressed and may contain confidential and/or privileg= ed material. If you received this in error, please contact the sender an= d delete the material from any system and destroy any copies.