Tungsten 2.0.6 setting sql_log_bin=0 while applying changes to slave

[GoogleCodeExporter]

What steps will reproduce the problem?

1.  On three servers (CentOS 6, MariaDB 5.5) do the following installs:
    Server 1: Primary MySQL master - startup MySQL.  This will act as primary master.
    Server 2: MySQL slave 1:  Setup mysql with log-slave-updates enabled in my.cnf. Create a slave user with replication privileges.
    Server 3: MySQL slave 2:  Setup mysql. Configure as native MySQL replication slave using "change master" command. Point this slave to MySQL slave 1 and start the slave process.
2.  Install Tungsten master/master replication between Server 1 and Server 2. 
You can use default options.  On server 2, ensure 
--skip-validation-check=MySQLNoMySQLReplicationCheck is specified to ignore the 
slave running there.
3.  On server 1, create a test table. 

What is the expected output?

Expected output should be the test table will show up in all three servers.  
Tungsten master/master replication would put the table on Server 2, and then 
MySQL replication would put the table on Server 3.

What do you see instead?

The table shows up in Server 2, but never shows up in Server 3.

What version of the product are you using?

2.0.6 community.  (By the way, this works just fine if you do it with 2.0.5).

On what operating system?

CentOS 6

Original issue reported on code.google.com by andrew.s...@miniclip.com on 27 Nov 2012 at 6:59

[GoogleCodeExporter]

Any updates on this?

Original comment by andrew.s...@miniclip.com on 30 Nov 2012 at 8:30

[GoogleCodeExporter]

Have you tried installing the Tungsten slave on #2 with --log-slave-updates?  I 
think this is not a bug but in fact just requires use of that value.   Let me 
know if that is the case. 

Cheers, Robert

Original comment by robert.h...@continuent.com on 6 Dec 2012 at 4:17

[GoogleCodeExporter]

Ok that seems to work.  Thank you.

I guess I should point out that this is not very well documented.  When I hit 
this issue, I searched all over for some setting for this and couldnt find it. 
I even started digging through the code.

At any right, this is now working for me. Thanks!

Andrew

Original comment by andrew.s...@miniclip.com on 6 Dec 2012 at 8:50

[GoogleCodeExporter]

I think "--log-slave-updates" should be documented.

I met this problem while I want to make a chain replication. I used 2.1.0.

Anyway, thanks.

Aaron

Original comment by dspun...@gmail.com on 21 Aug 2013 at 3:08