Bug #33423 Test 'rpl_server_id2' fails, likely random, but might have crashed server

• Submitted: 20 Dec 2007 22:38
• Modified: 18 Jan 2008 19:25
• Reporter: Kent Boortz
• Status: Can't repeat
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 5.0.54
• OS: MacOS (10.5 x86_64)
• Assigned to: Andrei Elkin
• CPU Architecture: Any

[20 Dec 2007 22:38] Kent Boortz

Description:
Test 'rpl_server_id2' fails, likely random,
but might have crashed server

  rpl_server_id2                 [ fail ]

  mysqltest: At line 9: query 'stop slave' failed: 2013: Lost connection to MySQL server during query

  The result from queries just before the failure was:
  stop slave;
  drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
  reset master;
  reset slave;
  drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
  start slave;
  create table t1 (n int);
  reset master;
  stop slave;

How to repeat:
Likely very hard to repeat, maybe by running the test
many times, possibly with some extra load on the host

  % ./mysql-test-run.pl rpl_server_id2 rpl_server_id2 ....

[17 Jan 2008 18:17] Andrei Elkin

There is no slave side error log available so I can only guess that 
STOP SLAVE might catch the state of the slave thread "unprepared" for shutting down.
Could it be a uninited active rli ... ?

Checking that.

[18 Jan 2008 19:25] Andrei Elkin

Further inspection of the code and some experimenting with delaying io, sql threads have not led to any finding except 
Bug #33931, Bug #33932.
It cannot be claimed these are the reason of the current as there was not error log left, which might have said a lot ...