List:General Discussion« Previous MessageNext Message »
From:Gleb Paharenko Date:December 28 2005 3:01pm
Subject:Re: Replication A->B->C - changes on B are not replicated to C
View as plain text  
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 problem. Research binary logs on B and check
if the statement which is not replicated is stored. In case it is stored ,
research relay logs on C. Remove filters if they're present on C to find
out if the problem in them.


"Frank Fischer" <frank.fischer@stripped> wrote:
>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 and table is beeing replicated from the
>relaylog. As Master there are also filters set, so not every database is
>written to the binlog. On B log-slave-updates is set.
>C replicates as a Slave of B and also has filters set, so not every database
>and table is replicated from B.
> 
>Now, there is a table system.subscribers. This table exists on A, B and C.
>This table is based on MyISAM, so i started the replication on B by calling
>LOAD DATA FROM Master. Same on C. This worked so far. Now when i change a
>record in the subscribers table, the changes are replicated from A to B and
>from B to C. That also works as expected. But now there is a field in the
>subscribers table, that will NEVER be changed on A but has to be changed on
>B. When i do such a change on B, i expect this change to be replicated to C
>but this does not happen. 
> 
>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?
> 
>Thanks a lot for your help.
> 
>Kind regards
>Frank


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   Gleb.Paharenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com



Thread
Replication A->B->C - changes on B are not replicated to CFrank Fischer28 Dec
  • Re: Replication A->B->C - changes on B are not replicated to CGleb Paharenko28 Dec
RE: Replication A->B->C - changes on B are not replicated to CFrank Fischer3 Jan
  • Re: Replication A->B->C - changes on B are not replicated to CGleb Paharenko6 Jan