From: Benjamin Stillman Date: September 24 2012 2:52pm Subject: RE: Doubt Regd. Circular Replication In Mysql List-Archive: http://lists.mysql.com/mysql/228248 Message-Id: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_A1CBEF39AA63D340951BAE325A3BA5A70F016E4CCOLMAILBOXP01Li_" --_000_A1CBEF39AA63D340951BAE325A3BA5A70F016E4CCOLMAILBOXP01Li_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable replicate-same-server-id =3D 0 keeps MySQL from replicating binary log entr= ies from itself. For instance, here's a rough overview: You write to Server A. Server A writes that to its binary log. Server B reads Server A's binary log and completes the same thing. Because log-slave-updates is enabled, Server B writes it to its own binary = log. Server C reads Server B's binary log and completes the same thing. Again, with log-slave-updates enabled, Server C writes it to its own binary= log. Server A reads Server C's binary log. Here's where the issue starts. Without replicate-same-server-id =3D 0, Serv= er A will complete the insert/update/delete as it reads it from Server C's = binary log. However, this query originated from Server A, so it's just goin= g to do it again. Then it's again replicated to Server B, Server C, and so = on. This can create a loop and/or break replication. For instance, if you d= rop a table on A. It replicates across, and back to A. Replication will err= or out because when it tries to drop the same table again, it already doesn= 't exist. You need replicate-same-server-id =3D 0 set so that it knows not = to execute any binary log entries with its own server ID. From: Adarsh Sharma [mailto:eddy.adarsh@stripped] Sent: Monday, September 24, 2012 10:39 AM To: Stillman, Benjamin Subject: Re: Doubt Regd. Circular Replication In Mysql Yes I fixed , but i solve the issue by enabling log-slave-updates only Why we use the below parameter :- replicate-same-server-id =3D 0 Ya i configured auto-increment settings properly. Thanks Thanks On Mon, Sep 24, 2012 at 8:03 PM, Stillman, Benjamin > wrote: Sounds like you're missing the following in your my.cnf on server B (probab= ly all of them): replicate-same-server-id =3D 0 log-slave-updates While you're checking, might as well as make sure your auto-increment setti= ngs are in there and correct also. -----Original Message----- From: Adarsh Sharma [mailto:eddy.adarsh@stripped] Sent: Monday, September 24, 2012 10:23 AM To: mysql@stripped Subject: Doubt Regd. Circular Replication In Mysql Hi all, Today i set up a circular replication between three nodes A,B & C successfu= lly. I expect whatever writes on A will propagated to B & then Propagated to C b= ecause the structure is like below :- A -> B - > C -> A I created a sample table stag in test database in A and insert few records = that are also replicated to B but not to C. Now when i created the same tab= le in C , it shows errors in show slave status\G output in A node. I needed this setup because all these servers are in different colos so th= at whatever writes to any node would replicated to others also for one data= base. I followed the below link for setting this circular replication :- http://www.howtoforge.com/setting-up-master-master-replication-on-four-node= s-with-mysql-5-on-debian-etch-p2 Is it possible to achieve whatever i needed or i need to create Multi Maste= r set up 2 nodes only. Thanks ________________________________ Notice: This communication may contain privileged and/or confidential infor= mation. If you are not the intended recipient, please notify the sender by = email, and immediately delete the message and any attachments without copyi= ng or disclosing them. LBI may, for any reason, intercept, access, use, and= disclose any information that is communicated by or through, or which is s= tored on, its networks, applications, services, and devices. --_000_A1CBEF39AA63D340951BAE325A3BA5A70F016E4CCOLMAILBOXP01Li_--