Bug #111709 | Error missing tablespace if innodb-validate-tablespace-paths=OFF | ||
---|---|---|---|
Submitted: | 10 Jul 2023 14:52 | Modified: | 3 Aug 2023 1:58 |
Reporter: | Huaxiong Song (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0.33 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[10 Jul 2023 14:52]
Huaxiong Song
[11 Jul 2023 8:49]
MySQL Verification Team
Hello Huaxiong Song, Thank you for the report and steps. Verified as described. regards, Umesh
[13 Jul 2023 7:37]
Jakub Lopuszanski
Thanks for reporting this! May I ask, what's your use case for disabling validation?
[13 Jul 2023 12:04]
Huaxiong Song
I'm doing some research on startup acceleration, which has similar characteristics to this parameter, so I found it. ^-^
[3 Aug 2023 1:58]
Huaxiong Song
After setting innodb_validate_tablespace_paths to OFF and running the test case, the failed cases can be found. Most of these problems are related to fil_space_t not being built in time. At the same time, there is also the problem that the old partition table(version < 8.0.18) move operation is not executed, which will also cause some problems. I think setting this parameter to OFF is very helpful to improve the startup speed (especially in the case of a large number of tables). A simple way to deal with it is: setting this parameter to OFF does not skip fil_ibd_open, but just skips validate_to_dd. Because inside fil_ibd_open, validate_to_dd is an IO operation, which takes most of the time compared to other memory operations.