How to solve the bug triggered by MySQL xtrabackup 2.4.12 backup

This article shows you how to solve the bug triggered by MySQL xtrabackup 2.4.12 backup. The content is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

First, background and phenomena:

Go to the production repository to direct a library with large traffic to be used as a slave database, and an error occurs (xtrabackup version: 2.4.12 MySQL version 5.7.23):

Second, the processing process

1) the first reaction, this bug should be everyone appeared, go to Google, but found nothing

2) well, it seems that you can only do it yourself. Since this is failing assertion:dir, the path should not be found. The mistake in reading the newspaper should have something to do with undo.

So I found the configuration file (in fact, I didn't open the separate undo here):

So I commented out the inndb_undo_directory and went on, but still reported an error.

I had no choice but to find the source code of 5.7.23 and navigate to line 928 of srv0start.cc that reported an error above.

It suddenly dawned on me that there is no separate table space directory in the online environment (and here we have to traverse the undo independent table space), so the temporary mkdir / data3/mysql/3307/undo;chown mysql:mysql / data3/mysql/3307/undo solution

The above content is how to solve the bug triggered by MySQL xtrabackup 2.4.12 backup. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.