Bug #17838 binlog not setup on seconday master after rename
Submitted: 1 Mar 2006 19:57 Modified: 14 Mar 2006 9:19
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.8 src OS:
Assigned to: Tomas Ulin CPU Architecture:Any

[1 Mar 2006 19:57] Tomas Ulin
see below

How to repeat:

create table t1 (a int key) engine=ndb;
insert into t1 values(1);
rename table t1 to t2;
insert into t2 values(2);

log in to secondary master...

show binlog events;

no write row event logged for t2...

also if you look in master.err1, the rename event is strange

[Note] NDB Binlog: rename table ./test/t1 -> ./test/t1.

Suggested fix:
workaround is to do show tables in secondary master, but one should not have to do that
[8 Mar 2006 23:10] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[9 Mar 2006 14:06] Tomas Ulin
pushed to 5.1.8
[14 Mar 2006 9:19] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented bugfix in 5.1.8 changelog; closed.