| Bug #52757 | replication issue when replication done through a federated db | ||
|---|---|---|---|
| Submitted: | 12 Apr 2010 8:40 | Modified: | 12 May 2010 9:21 |
| Reporter: | sweekar k | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Federated storage engine | Severity: | S2 (Serious) |
| Version: | 5.0.45 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | federated engine replication | ||
[12 Apr 2010 9:07]
Sveta Smirnova
Thank you for the report. But version 5.0.45 is old and many bugs were fixed since. Please try current version 5.0.90 and inform us if problem still exists.
[12 Apr 2010 9:17]
sweekar k
i have checked in 5.0.51b-log it exists even in this version , ll get a setup of 5.0.90 and check
[12 May 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".
Description: set up : master db where all the write happens federated db which is a connection to the slave db slave db where replication is configured as slave to the master using the fedrated engine Problem : although data is properly populated in all the tables of the master db ,In the slave dbs some columns happen to be null these columns have datatype as varchar. This problem does not occur when replication is done without a federated db connection replication is done form the mysql client using the start slave command . the start position and the end master currnt postion are changed everytime a start slave is done How to repeat: create a replication set up master myisam engine replication through federated db slave innodb engine run replication continuously using the start slave command changing the start position.