From: Rick James
Date: October 27 2010 8:00pm
Subject: rbr and reloaded slave (from mysqldump) ?
List-Archive: http://lists.mysql.com/replication/1980
Message-Id: <4CC884E8.1000808@yahoo-inc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  Background:
* 250GB table - PARTITIONed InnoDB; file_per_table
* RBR used
* Slave is hosed
* Sane ways of repairing the slave has been ruled out (it's a long story).

Plan A:  Reload PARTITIONs by copying .ibd files. -- Rumor has it that 
this will fail due to tablespace number (or something) being buried in 
each .ibd.  Such would make file copies of .ibd from a different machine 
not work.
Question 1:  Is this rumor true?

Plan B:  We have a mysqldump and could reload.  But, will RBR be 
confused by the InnoDB blocks being slightly different after this load.
Question 2:  What is the low level info in a RBR item?  Does it include 
a 'block number', which would probably be invalid after the reload?  Or 
does it contain something like the PK, which should be impervious?

-- 

Rick James - MySQL Geek