MySQL Forums
Forum List  »  NDB clusters

Problem with Master Master Replication
Posted by: Bruno Rothbächer
Date: December 03, 2013 09:08AM

Hello,
I've created 2 Cluster with have to replicate.
After I setup the cluster and started it it works fine.
ndb_mgm show me on Server 1:
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=11 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3, Nodegroup: 0, *)
id=12 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3)

[mysqld(API)] 1 node(s)
id=51 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3)

On Server 2 it shows;
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=11 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3, Nodegroup: 0, *)
id=12 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3)

[mysqld(API)] 1 node(s)
id=51 @127.0.0.1 (mysql-5.6.14 ndb-7.3.3)

I've tried to create tables and save data to them. The replication works.

But after I tried to shutdown one of the server and started it again I get a lot of error messages in the log files like:
Slave SQL: The incident LOST_EVENTS occured on the master. Message: mysqld startup, Error_code: 1590
Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'tms-***-bin.000003' position 120

It's not possible for to reactivate the replication.
I've tried:
stop slave;
SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
start slave;

But it don't worked.

What can I do?

Thanks a lot

Bruno Rothbaecher

Options: ReplyQuote


Subject
Views
Written By
Posted
Problem with Master Master Replication
1766
December 03, 2013 09:08AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.