MySQL Bugs: #78200: During Mysql cluster replication, slave thread is periodically crashing

Bug #78200	During Mysql cluster replication, slave thread is periodically crashing
Submitted:	25 Aug 2015 7:30	Modified:	7 Nov 2019 14:38
Reporter:	Nitin Sharma	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S3 (Non-critical)
Version:	5.6.20	OS:	Red Hat
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	replication

Description:

We have a Master Slave MySQL cluster.. Master Mysql cluster has 2 nodes and Slave MySQL Cluster also has 2 servers.

We are using Mysql version as 5.6.20 and NDB version is 7.3.6

When the replication is initiated, on my slave MySQL Cluster I observe following messages in my mysql error file:-

2015-06-26 10:13:48 2731 [Note] Error reading relay log event: slave SQL thread was killed 2015-06-26 10:13:48 2731 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013) 2015-06-26 10:13:48 2731 [Note] Slave I/O thread killed while reading event 2015-06-26 10:13:48 2731 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000059', position 129077943 2015-06-26 10:13:48 2731 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.104.170.142', master_port= 3306, master_log_file='mysql-bin.000059', master_log_pos= 129077943, master_bind=''. New state master_host='10.104.170.142', master_port= 3306, master_log_file='mysql-bin.000059', master_log_pos= 129077943, master_bind=''. 2015-06-26 10:13:48 2731 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. 2015-06-26 10:13:48 2731 [Warning] Slave SQL: If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0 2015-06-26 10:13:48 2731 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000059' at position 129077943, relay log './spf_relay_bin.000001' position: 4 2015-06-26 10:13:48 2731 [Note] Slave I/O thread: connected to master 'SPFrepluser@10.104.170.142:3306',replication started in log 'mysql-bin.000059' at position 129077943 2015-06-26 10:13:49 2731 [Note] NDB Slave : MaxReplicatedEpoch set to 0 (0/0) at Slave start

On further googling i found this is an existing issue and for this I also applied following three parameters in the my.cnf relay-log-recovery = 1 relay-log-info-repository = TABLE master_info_repository = TABLE

After this i restarted my mysql and performed START SLAVE as well. Still this issue exists.

Please share the solution or pointers to proceed further

How to repeat:
This is a recursive behavior which is seen on the Slave servers.

Hi,

It is unclear from your report do you have MySQL Cluster to MySQL server replication or you have MySQL Cluster to MySQL Cluster replication. 

Can you please
 - give us the full config of the whole system (all nodes)
 - give us the ndb_error_report from all the mysql clusters
 - give us mysql error log from all sql nodes

so we can analyze situation properly
thanks

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