Bug #53614 | ROW-base binlog result in different data . | ||
---|---|---|---|
Submitted: | 13 May 2010 5:12 | Modified: | 7 Aug 2010 7:36 |
Reporter: | He yunfei | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S1 (Critical) |
Version: | 5.1.40, 5.1.48-bzr | OS: | Any |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
Tags: | ALTER TABLE, RBR, table schemas |
[13 May 2010 5:12]
He yunfei
[26 May 2010 20:26]
Sveta Smirnova
Thank you for the report. Verified as described, but only with row binlog format. With mixed everything works fine. Test case: --source include/master-slave.inc --source include/have_innodb.inc set names gbk; drop table if exists h1 ; create table h1 (id int , name varchar(20),comment varchar(500 ) , primary key (id)) engine=innodb default charset =gbk ; insert into h1 values (1,'h1','h111'), (2,'h2','h112'), (3,'h3','h113'), (4,'h4','h114'), (5,'h5','h115'); flush logs ; sleep 1; connection slave; stop slave; connection master; update h1 set name='h-m@2' where id=5; insert into h1 (id, name, comment) values (6,'h6@2','dsflk'); connection slave; alter table h1 add addr varchar(500) after name ; select * from h1; start slave; sleep 1; select * from h1; Master option file: --binlog-format=row With next-mr replication fails with error which in my opinion is correct.
[27 May 2010 2:01]
He yunfei
Thx for your reply . But I cann't image what's you result . and may be your option file is not same with mine. eg: tx_isolation=? binlog_format=?
[27 May 2010 2:01]
He yunfei
Thx for your reply . But I cann't image what's you result . and may be your option file is not same with mine. eg: tx_isolation=? binlog_format=?
[27 May 2010 8:43]
Sveta Smirnova
Same output like in the initial description: select * from h1; id name addr comment 1 h1 NULL h111 2 h2 NULL h112 3 h3 NULL h113 4 h4 NULL h114 5 h-m@2 h115 h115 6 h6@2 dsflk NULL
[1 Jun 2010 18:13]
Jon Stephens
Corrected Lead.
[2 Jun 2010 1:54]
guanding jin
The problem is exist,that is concealed.suggestion:alter architecture to avoid problem;
[2 Jun 2010 2:13]
He yunfei
HI, Sveta Smirnova in fact , I don't very understand what your means ; The result is correct ? with App , or With you ? May be we should stand with App and to handle them .
[7 Jun 2010 20:35]
Jon Stephens
He Yunfei, Guanding Jin, Hello! After analysis and discussion with Replication developers, we have concluded that this is expected behaviour, and that your problem is similar to the issue encountered in BUG#51406 (order of columns in the table must remain the same on both master and slave). I'm working on adding a better explanation/examples to the Manual, and I will update this bug report when that is done. Thanks! Jon Stephens MySQL Documentation Team Stockholm
[7 Aug 2010 6:33]
Jon Stephens
Set target version, priority.
[7 Aug 2010 7:36]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Updated http://dev.mysql.com/doc/refman/5.1/en/replication-features-differing-tables.html#replicat... with more info and an example. Also added to 5.5/5.6/6.0 versions of this section. Closed.