On 09/24/2013 08:41 AM, Roberto Spadim wrote:
this could happen, or replication know when it do a "loop" at replication? i'm not sure if i'm right, but since A is master of B, and B act as a slave for first update, i think it will not replicate to A, i'm right?
that's why each participant in a replication setup needs to have a unique server_id so that it can identify replication events that originated from itself and ignore them. Also a mysql server that acts as both replication master (writing its own binlogs) and slave (receiving binlog events from another master) will only forward replication events received from its master to its own binlog if log_slave_updates is enabled which is off by default. See also: https://dev.mysql.com/doc/refman/5.5/en/replication-options-binary-log.html#... http://dev.mysql.com/doc/refman/5.5/en/replication-options.html#option_mysql... -- Hartmut Holzgraefe, Principal Support Engineer (EMEA) SkySQL | http://www.skysql.com/