Sounds like you're missing the following in your my.cnf on server B (probably
all of them):
replicate-same-server-id = 0
log-slave-updates
While you're checking, might as well as make sure your auto-increment settings
are in there and correct also.
-Original Message-
From: Adarsh
: Adarsh Sharma [mailto:eddy.ada...@gmail.com]
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 = 0
Hello Benjamin,
On 9/24/2012 10:52 AM, Stillman, Benjamin wrote:
replicate-same-server-id = 0 keeps MySQL from replicating binary log entries
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
I stand corrected and apologize. Numerous multi-master setup descriptions I've
read have said to set this (including the one linked in the original question).
However, as you said, the entry in the manual clearly says it defaults to 0.
Learn something new every day. Thanks Shawn.
On Sep 24,
24, 2012 11:56 AM
To: Shawn Green
Cc: mysql@lists.mysql.com
Subject: Re: Doubt Regd. Circular Replication In Mysql
I stand corrected and apologize. Numerous multi-master setup
descriptions I've read have said to set this (including the one linked
in the original question). However, as you
on your hands to
fix the broken replication.
-Original Message-
From: Stillman, Benjamin [mailto:bstill...@limitedbrands.com]
Sent: Monday, September 24, 2012 11:56 AM
To: Shawn Green
Cc: mysql@lists.mysql.com
Subject: Re: Doubt Regd. Circular Replication In Mysql
I stand
