MySQL Bugs: #44566: Error on Innodb to NDB replication with UPDATE statements

Bug #44566	Error on Innodb to NDB replication with UPDATE statements
Submitted:	30 Apr 2009 3:53	Modified:	6 Jun 2009 9:31
Reporter:	kasun Ekanayake	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-6.3	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	mysql-5.1.30 ndb-6.3.20

Description:
Hi,
   I installed a mysql cluster.
---------------
id=2    @192.168.19.92  (mysql-5.1.30 ndb-6.3.20, Nodegroup: 0, Master)
id=3    @192.168.19.93  (mysql-5.1.30 ndb-6.3.20, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @192.168.19.91  (mysql-5.1.30 ndb-6.3.20)

[mysqld(API)]   2 node(s)
id=4    @192.168.19.91  (mysql-5.1.30 ndb-6.3.20)
id=5    @192.168.19.93  (mysql-5.1.30 ndb-6.3.20)

---------------
All servers run in linux

And 192.168.19.91 act as master in master-master replication with another mysqld (innodb).

There is mysqld running with solaris 10.
192.168.140.92
5.1.30-log

This also act as master with above mentioned sql node.

Problem comes only with UPDATE from NDB -- > Innodb (192.168.19.91 to 192.168.140.92). UPDATE statements execute on SQL node on cluster.

INSERT , DELETE and UPDATE from Innodb --> NDB (192.168.140.92 to 192.168.19.91)  is working fine.

error
---------------
090430 10:26:02 [ERROR] Slave SQL: Could not execute Write_rows event on table radius.telko; Duplicate entry '2' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.000083, end_log_pos 141725255, Error_code: 1062
090430 10:26:02 [Warning] Slave: Duplicate entry '2' for key 'PRIMARY' Error_code: 1062
090430 10:26:02 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000083' position 141725035

---------------

PLease help

How to repeat:
Run UPDATE statment on one of the SQL nodes and check data integrity on Innodb. Check db logs on Innodb

Thank you for the report.

I can not repeat described behavior with test data. Please indicate which binlog_format you are using and provide examples of problem UPDATE statements.

i have fixed the problem. I have put
binlog-format=STATEMENT

So it works. sorry for late reply. I think you refer to the same. thanks for the help

BTW I like to know is it recommend to use this kind of a architecture. Having replication between innnodb abd ndb? . How much of testing had been done on this area.

please comment

i have fixed the problem. I have put
binlog-format=STATEMENT

So it works. sorry for late reply. I think you refer to the same. thanks for the help

BTW I like to know is it recommend to use this kind of a architecture. Having replication between innnodb abd ndb? . How much of testing had been done on this area.

please comment

Statement format logs do not really work with cluster, try setting ndb_log_update_as_write to OFF instead and keep the row based log format.

As your cluster has two mysqld servers you may also consider to set up
two replication channels on the cluster side so that events don't get
lost when the logging mysqld is down:

http://dev.mysql.com/doc/mysql-cluster-excerpt/5.1/en/mysql-cluster-replication-two-channe...

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".

Finding a bug in the ode is a very difficult thing. If I would give you some sort of opinion by https://essay-reviewer.com/best-paper-writing-service/ then this will act like a life-changing decision for you. Post your program here and tell your problem the experts here will go through your code and will find the problematic bug.

thanks

can you take a look at my website with a similar problem? https://www.datasciencecentral.com/