hi,all
I also came into the almost same situation, my migration like below:
1. use xtrabackup back a mysql5.5.x database
2. set up the first node of PXC5.6 with the backup
3. start the master-slave replication between mysql5.5 and the first node of pxc5.6
4. add new node to the PXC5.6
when i process the step 4, I found the replication is stopped caused by the auto-increment issue.
And i found the binlog-format of mysql5.5.x is statement-based, So i setup a middle node with row
based binlog as the master of PXC, and it works. the operation steps like below:
1. use xtrabackup back a mysql5.5.x database
2. setup a middle node mysql5.6.x with the backup and binlog-format=row
3. start the master-slave replication between mysql5.5 and mysql5.6.x
4. set up the first node of PXC5.6 with the backup
5. start the master-slave replication between mysql5.6.x and the first node of pxc5.6
6. add new node to the PXC5.6
I do not deep into find the reason, but i know there must be something different for pxc and normal slave
at the method of handling auto-increment field,So with row-based binlog, there is no need to handle the
auto-increment field values, and the behaviour of them will be the same.