MDEV-37795 - MariaDB start up spits DDL_LOG: Got error 1033 #4552
+54
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
innodb_fts.crash_recovery,release fails sporadically. In release build it silently disables sync points, which allows server to crash at aribitrary point of DDL, specifically when .frm file is created but not yet written. Subsequent attempt to open such table at recovery (needed to obtain number of high-level indexes) leads to OPEN_FRM_CORRUPTED error rather than something like "file not found" (which is ignored by recovery). Emitted errors were not handler by mtr. Silently ignore newly created corrupt .frm during recovery. High-level indexes were most probably not created at this point. It is still probable that .frm got corrupted after high-level indexes were created. In this case recovery won't be able to handle stale high-level indexes and they will be preserved. This regression was introduced by "d50663198c0 DDL recovery for high-level indexes".
github-actions
bot
added
the
External Contribution
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
innodb_fts.crash_recovery,release fails sporadically. In release build it silently disables sync points, which allows server to crash at aribitrary point of DDL, specifically when .frm file is created but not yet written.
Subsequent attempt to open such table at recovery (needed to obtain number of high-level indexes) leads to OPEN_FRM_CORRUPTED error rather than something like "file not found" (which is ignored by recovery). Emitted errors were not handler by mtr.
Silently ignore newly created corrupt .frm during recovery. High-level indexes were most probably not created at this point.
It is still probable that .frm got corrupted after high-level indexes were created. In this case recovery won't be able to handle stale high-level indexes and they will be preserved.
This regression was introduced by "d50663198c0 DDL recovery for high-level indexes".