[MDEV-7975] sporadic failure in test case rpl.rpl_gtid_startpos Created: 2015-04-10  Updated: 2015-04-14  Resolved: 2015-04-14

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0, 10.1
Fix Version/s: 10.0.18, 10.1.5

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: gtid, replication


 Description   

For example:

rpl.rpl_gtid_startpos 'innodb_plugin,stmt' w1 [ fail ]
 
Found warnings/errors in server log file!
 
Test ended at 2015-04-09 20:30:43
 
line
 
150409 20:30:42 [ERROR] Slave I/O: Setting @slave_connect_state failed with error: Lost connection to MySQL server during query, Internal MariaDB error code: 2013
 
^ Found warnings in /opt/buildbot-slave/mariadb/dan_demeter2/build/mysql-test/var/1/log/mysqld.2.err
 

rpl.rpl_gtid_startpos 'row,xtradb' w1 [ fail ]
 
Found warnings/errors in server log file!
 
Test ended at 2015-04-09 14:16:40
 
line
 
150409 14:16:39 [ERROR] Slave I/O: The slave I/O thread stops because master does not support MariaDB global transaction id. A fatal error is encountered when it tries to SELECT @@GLOBAL.gtid_domain_id. Error: Lost connection to MySQL server during query, Internal MariaDB error code: 2013
 
^ Found warnings in /dev/shm/var_auto_rn2P/1/log/mysqld.2.err

This looks to be caused by the IO thread being killed (eg. by STOP SLAVE) in
the test before it has completed connecting to the server.

That last error probably also indicates a missing check for
is_network_error(). It is not intended that the slave should declare the
master not supporting GTID just because of a temporary network connection.

 Comments   
Comment by Kristian Nielsen [ 2015-04-14 ]

http://lists.askmonty.org/pipermail/commits/2015-April/007746.html

Generated at Thu Feb 08 07:23:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.