Bug #15886 Test: Timing issue in test "rpl_until"
Submitted: 20 Dec 2005 12:06 Modified: 11 May 2006 16:15
Reporter: Joerg Bruehe
Status: Can't repeat
Category:Server: Replication Severity:S2 (Serious)
Version:5.0.17, 5.1.4 and up OS:various Unix
Assigned to: Mats Kindahl Target Version:

[20 Dec 2005 12:06] Joerg Bruehe
Description:
This is a longer-standing issue, originally reported as bug#12429.
Most occurrences were deemed "irrelevant" and avoided by using "--replace-column", as
discussed at some length by Guilhem in that issue.

However, one issue is still occurring, and I am not yet sure whether that can also be
handled in this way - this is the "show slave status" following the comment
"# here the sql slave thread should be stopped"

-------------------------------------------------------
*** r/rpl_until.result
--- r/rpl_until.reject
***************
*** 55,61
  start slave until master_log_file='master-bin.000001', master_log_pos=776;
  show slave status;
  Slave_IO_State        Master_Host     Master_User     Master_Port     Connect_Retry  
Master_Log_File Read_Master_Log_PosRelay_Log_File   Relay_Log_Pos   Relay_Master_Log_File
  Slave_IO_Running        Slave_SQL_Running       Replicate_Do_DB Replicate_Ignore_DB
Replicate_Do_Table      Replicate_Ignore_Table  Replicate_Wild_Do_Table
Replicate_Wild_Ignore_Table     Last_Errno  Last_Error      Skip_Counter   
Exec_Master_Log_Pos     Relay_Log_Space Until_Condition Until_Log_File  Until_Log_Pos    
  Master_SSL_Allowed      Master_SSL_CA_File      Master_SSL_CA_Path      Master_SSL_Cert
Master_SSL_Cipher       Master_SSL_Key      Seconds_Behind_Master
! #     127.0.0.1       root    MASTER_MYPORT   1       master-bin.000001       776    
slave-relay-bin.000004  #       master-bin.000001   Yes     No                           
                          0               0       776     #       Master     
master-bin.000001       776     No                                              #
  start slave until master_log_file='master-bin', master_log_pos=561;
  ERROR HY000: Incorrect parameter or combination of parameters for START SLAVE UNTIL
  start slave until master_log_file='master-bin.000001', master_log_pos=561,
relay_log_pos=12;
--- 55,61
  start slave until master_log_file='master-bin.000001', master_log_pos=776;
  show slave status;
  Slave_IO_State        Master_Host     Master_User     Master_Port     Connect_Retry  
Master_Log_File Read_Master_Log_PosRelay_Log_File   Relay_Log_Pos   Relay_Master_Log_File
  Slave_IO_Running        Slave_SQL_Running       Replicate_Do_DB Replicate_Ignore_DB
Replicate_Do_Table      Replicate_Ignore_Table  Replicate_Wild_Do_Table
Replicate_Wild_Ignore_Table     Last_Errno  Last_Error      Skip_Counter   
Exec_Master_Log_Pos     Relay_Log_Space Until_Condition Until_Log_File  Until_Log_Pos    
  Master_SSL_Allowed      Master_SSL_CA_File      Master_SSL_CA_Path      Master_SSL_Cert
Master_SSL_Cipher       Master_SSL_Key      Seconds_Behind_Master
! #     127.0.0.1       root    MASTER_MYPORT   1       master-bin.000001       776    
slave-relay-bin.000004  #       master-bin.000001   No      No                           
                          0               0       776     #       Master     
master-bin.000001       776     No                                              #
  start slave until master_log_file='master-bin', master_log_pos=561;
  ERROR HY000: Incorrect parameter or combination of parameters for START SLAVE UNTIL
  start slave until master_log_file='master-bin.000001', master_log_pos=561,
relay_log_pos=12;
-------------------------------------------------------

(Line numbers of 5.1.4)

OCCURRED:
hammer-glibc23-5.1-max.log   normal
hammer-glibc23-5.1-max.log   ps-protocol
intelxeon3-5.1-max.log   normal
rhas3-x86-glibc23-5.1-max.log   normal
sol10-amd64-a-5.1-max.log   ps-protocol
sunfire100b-5.1-max.log   normal

Similar occurrence in 5.0.17, so a fix is needed in 5.0 already.

How to repeat:
Test suite failure.
[12 Feb 2006 10:42] Kent Boortz
The test case put into "disabled.def" again, and priority increased.
[11 May 2006 16:15] Mats Kindahl
Unable to repeat the failure in the latest version of 5.0 and 5.1.