Bug #54627 Replication Fails
Submitted: 19 Jun 2010 6:56 Modified: 21 Jul 2010 6:10
Reporter: Devang Modi Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:mysql Ver 14.12 Distrib 5.0.45 OS:Linux (Linux Teak12 2.6.18-128.el5)
Assigned to: CPU Architecture:Any
Tags: alter, fails, not, processing, replication, table

[19 Jun 2010 6:56] Devang Modi
Dear Supporter;

We are using mysql product that is having 1 innodb  database and 20 MyIsam database instance.

For same server we have two replication server in same network.

I observed that when issue "Alter table " for adding field in tables those are resting in innodb as well myisam it successfully proceed on Main (Master) server but the affect on Slave (child) server only we found in innodb database instance.

The database instance running with MyIsam tables are not getting affect with "Alter table command" on slave only.

I also searched for binlog created on Master server and surprisingly it is only having "Alter table " for innodb database instance only but not MyIsam .

Details example

Master Server
      Database Name : CVT 
      Table Name: cvt.T1 Engine type Innodb
      Alter Table: Add field F1

      Database Name : CVTA0001  
      Table Name: CVTA0001.T1 Engine type MyIsam
      Alter Table: Add field F1

Alter command executed perfectly.

But bin log records query for database CVT only and skip for CVTA0001

Due to same reason Replication server - slave did not get same query for them

for your referece I am attaching my.cnf also related to master


How to repeat:
Please see description
[21 Jun 2010 6:10] Sveta Smirnova
Thank you for the report.

But version 5.0.45 is old and many ugs were fixed since. Please try current version 5.0.91 and inform us if problem still exists.
[21 Jul 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".