Hello.
My conclusion so far: The data is in the relay-log on C but it's not put
into the database for some reason. I simply have no clue what reason it
could be. In fact i'm a little bit confused right now so any help is
very welcome.
In you original message you told you were working
a little bit confused right now so any help is
very welcome.
Greetings
Frank
From: Glebnbsp;PaharenkoDate: December 28 2005 4:01pm
Subject: Re: Replication A-B-C - changes on B are not replicated to C
Hello.
So now my question is: is it basically possible to do this or doesn't mysql
Hi all
i have a question related to replication on 4.0.x.
I have the following setup:
A - B - C
A is a Master and writes all changes to its binlog (meaning there is no
filter set).
B acts as Slave from A and as Master for C. As a Slave B has filters set, so
not every change of every database
Hello.
So now my question is: is it basically possible to do this or doesn't mysql
replication mechanism support this setup? If it is possible: Any idea where
the problem could be? If it's not possible: any idea for a different setup
that would allow to this?
You should localize the
Hello all:
I have set the repliaction between A and B server successfully.
While the B server replicate the data from A server,we fould the relay log
refreshing.But the master log has no change.
Since we want to add a Server C to replicate the Server B, the master log must
existing
From http://dev.mysql.com/doc/mysql/en/Replication_Options.html
--log-slave-updates
Normally, updates received from a master server by a slave are not
logged to its binary log. This option tells the slave to log the updates
performed by its SQL thread to the slave's own binary log. For this
