Re: InnoDB Cluster Replication Issue

[Philip Krauss]

In an early setup I did of innodb cluster I had a mysql 5.7 database I was using for testing. In this database I was loading some random metadata from another app. When I decided to convert this to innodb cluster I dropped the database and made a vm image for cloning. When that was done I had 3 nodes that as far as I could tell were all set after proper renaming.

However after creating the cluster and adding the second node I was getting "No <database_name> to drop". Simple enough right I don't expect that database to be there, so I ran a reset master on the second node to wipe out the binlogs. What should have occurred to me but didn't was that this would be a perpetual issue if not corrected from the start.

I fixed this myself by dropping the vm's, going back to my original image and wiping the binlogs. When I started with fresh binlogs I never saw this problem again. With innodb cluster if you are prepping a node that is to not be replicated or used for node recovery do:

SET sql_log_bin = 0;
Create user bob;
SET sql_log_bin = 1;



Edited 2 time(s). Last edit at 04/06/2018 03:55AM by Philip Krauss.