LP:714419 - Replication failures with slave provisioning via mysqldump and tables with no PK

The following test fails in mysql 5.1, maria-5.2 and maria-5.2-rpl, but passes under mysql 5.5 . The test operates as follows:

1. A transactional concurrent UPDATE workload is maintained on the master throughout the test;

2. Around the middle of the test, a new slave is provisioned via mysqldump (port 19304, datadir and logs in mysql-test/var/master-data_clonedslave) and then started;

3. At the end of the test, the new slave is checked via SHOW SLAVE STATUS and dumped and compared to the master

There is a separate slave, on port 19304 that is not provisioned via mysqldump. It replicates properly and is not relevant to this particular bug )

The slave reports either:

110207 9:04:37 [ERROR] Slave SQL: Error 'Table 'test.table1_innodb_int' doesn't exist' on opening tables, Error_code: 1146
110207 9:04:37 [Warning] Slave: Table 'test.table1_innodb_int' doesn't exist Error_code: 1146

even though the table does exist on the slave and the workload does not contain any DDL statements

or

110207 9:37:17 [ERROR] Slave SQL: Could not execute Update_rows event on table test.table100_innodb; Can't find record in 'table100_innodb', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log master-bin.000001, end_log_pos 7833035, Error_code: 1032

This issue seems to be releated to the more general problem of replicating tables with no PK, even though in this particular test, straightforward replication does work – what does not work is provisioning a new slave via mysqldump. Extensive fixes for PK-less replication were done for 5.5 .