PS-9322 fix: With super_read_only=1, undo truncation cannot update DD and leaves orphan truncate log files (8.0) #5415
Conversation
This file contains 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
… and leaves orphan truncate log files https://perconadev.atlassian.net/browse/PS-9322 Backported Oracle fix for Bug #35784192 "tablespace is missing for table innodb_undo_002" (commit mysql/mysql-server@bda098a and mysql/mysql-server@97f4285) from 8.4 to 8.0. Bug#35784192 tablespace is missing for table innodb_undo_002 This bug reports following two problems: Querying the information schema reports undo tablespace is missing - while an undo file is present. Purge threads don't remove the undo_space_number_trunc.log file. While the first problem is already fixed through Bug#32104924, Bug#32654667 This bug fix aims to address the second problem. The purge thread attempts to lock dictionary tables, while truncating the undo tablespace. This lock can't be acquired in a read-only MySQL instance, except when the thread has some special flags associated with it. In this case, we use the skip_readonly_check member of the thread descriptor struct, to signal that the readonly check should not be applied to the purge thread. This is done via the set_skip_readonly_check() method. Change-Id: Iea6255ff6654752db8658bdd422cc3e58e3a8a97 Bug#35784192 tablespace is missing for table innodb_undo_002 [postfix] Remove MySQL versions number from MTR test. Change-Id: I3973435edbbc8bf442846c617ade4b5b824bb8c2
satya-bodapati
approved these changes
Sep 11, 2024
percona-ysorokin
merged commit 6e13886
into
percona:release-8.0.39-30
27 of 28 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://perconadev.atlassian.net/browse/PS-9322
Backported Oracle fix for Bug #35784192
"tablespace is missing for table innodb_undo_002"
(commit mysql/mysql-server@bda098a and mysql/mysql-server@97f4285) from 8.4 to 8.0.
Bug#35784192 tablespace is missing for table innodb_undo_002
This bug reports following two problems:
Querying the information schema reports undo tablespace is missing -
while an undo file is present.
Purge threads don't remove the undo_space_number_trunc.log file.
While the first problem is already fixed through Bug#32104924, Bug#32654667
This bug fix aims to address the second problem.
The purge thread attempts to lock dictionary tables, while truncating the undo tablespace. This lock can't be acquired in a read-only MySQL instance, except when the thread has some special flags associated with it. In this case, we use the skip_readonly_check member of the thread descriptor struct, to signal that the readonly check should not be applied to the purge thread. This is done via the set_skip_readonly_check() method.
Change-Id: Iea6255ff6654752db8658bdd422cc3e58e3a8a97
Bug#35784192 tablespace is missing for table innodb_undo_002 [postfix] Remove MySQL versions number from MTR test.
Change-Id: I3973435edbbc8bf442846c617ade4b5b824bb8c2