Bug #18933 initial slave synchronization with FILE and POS does not work
Submitted: 10 Apr 2006 8:06 Modified: 15 Jan 2007 16:36
Reporter: patrice audigou Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S1 (Critical)
Version:5.1.8.beta OS:Linux (redhat9)
Assigned to: Tomas Ulin CPU Architecture:Any

[10 Apr 2006 8:06] patrice audigou
Description:
initial slave (5.1.8.beta) synchronization with FILE and POS does not work if the 
master is in release 5.1.2-a_drop5p11. The replication process seems pending.

On the master side the binlog_index table contents :
==================================
 
+----------+-------------------------+-------+---------+---------+---------+-----------+
| Position | File                    | epoch | inserts | updates | deletes | schemaops |
+----------+-------------------------+-------+---------+---------+---------+-----------+
|     1619 | ./lalxp23827-bin.000001 |    29 |    2618 |       0 |       0 |         0 |
|  1706169 | ./lalxp23827-bin.000001 |    30 |    3135 |       0 |       0 |         0 |
|  4513840 | ./lalxp23827-bin.000001 |    31 |    3099 |       0 |       0 |         0 |
|  9686303 | ./lalxp23827-bin.000001 |    32 |    1148 |       0 |       0 |         0 |
+----------+-------------------------+-------+---------+---------+---------+-----------+

I try to synchronize the Slave with the following command :
========================================

-> change master to 
-> MASTER_LOG_FILE="lalxp23827-bin.000001",
-> MASTER_LOG_POS=1619;
-> start slave;

->show slave status\G;
*************************** 1. row ***************************
             Slave_IO_State: Waiting for master to send event
                Master_Host: lalxp23827
                Master_User: root
                Master_Port: 3306
              Connect_Retry: 1
            Master_Log_File: lalxp23827-bin.000001
        Read_Master_Log_Pos: 11602547
             Relay_Log_File: relay.000063
              Relay_Log_Pos: 248
      Relay_Master_Log_File: lalxp23827-bin.000001
           Slave_IO_Running: Yes
          Slave_SQL_Running: Yes
            Replicate_Do_DB:
        Replicate_Ignore_DB:
         Replicate_Do_Table:
     Replicate_Ignore_Table:
    Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
                 Last_Errno: 0
                 Last_Error:
               Skip_Counter: 0
        Exec_Master_Log_Pos: 11602547
            Relay_Log_Space: 248
            Until_Condition: None
             Until_Log_File:
              Until_Log_Pos: 0
         Master_SSL_Allowed: No
         Master_SSL_CA_File:
         Master_SSL_CA_Path:
            Master_SSL_Cert:
          Master_SSL_Cipher:
             Master_SSL_Key:
      Seconds_Behind_Master: 0
1 row in set (0.00 sec)

the log file mysqld-err.trace contents 
========================

060410 10:56:18 [Note] Slave SQL thread initialized, starting replication in log 'lalxp23827-bin.000001' at position 1619, relay log '/var/relaylog/relay.000001' position: 4
060410 10:56:18 [Note] Slave I/O thread: connected to master 'root@lalxp23827:3306',  replication started in log 'lalxp23827-bin.000001' at position 1619

How to repeat:
/*--*/
[12 Sep 2006 6:57] Daniel Stricot
I retried the test shown in bug 18933, with the master using mysql
-> version V5.1.2DROP5P14, and the slave using mysql version V5.1.12-BETA.
-> I got the same result : no replication, the replication process seems
-> pending.
-> Will this bug be corrected?
[8 Jan 2007 23:19] Jonathan Miller
Hi,

I tried to retest this using drop 16 and the latest telco release clones. I tried to upgrade the ndb slave cluster in 3 different ways all of which currently fail.

1) Do a backup and try to restore.

Nodeid = 2
Backup Id = 1
backup path = ./
Ndb version in backup files: ndb-5.1.3
Restore program incompatible with backup versions between ndb-5.1.3 and ndb-5.1.3

NDBT_ProgramExit: 1 - Failed

2) Restart each data node with -i
Time: Monday 8 January 2007 - 23:07:16
Status: Temporary error, restart node
Message: Pointer too large (Internal error, programming error or missing error message, please report a bug)
Error: 2306
Error data: dbdih/DbdihMain.cpp
Error object: DBDIH (Line: 13443) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 4725
Trace: /space/run/ndb_2_trace.log.2
Version: mysql-5.1.14 ndb-6.1.1-beta
***EOM***

3) Take cluster down and try to restart without --initial
Time: Monday 8 January 2007 - 22:07:09
Status: Temporary error, restart node
Message: Pointer too large (Internal error, programming error or missing error message, please report a bug)
Error: 2306
Error data: dbdih/DbdihMain.cpp
Error object: DBDIH (Line: 13443) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 4193
Trace: /space/run/ndb_2_trace.log.1
Version: mysql-5.1.14 ndb-6.1.1-beta
***EOM***