Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
N/A
-
None
Description
Likely caused by MDEV-18976, innodb_undo_log_truncate=ON lost its crash-safety status. The reason is that the pages of the being-truncated undo log tablespace were not marked as modified by the mini-transaction. The logic of logging page-free operations was changed in MDEV-18976.
The failures are rare and hard to repeat, but there is some indication that a small fix to trx_purge_free_segment() would fix this.
I did not find any matching failures of the test innodb.undo_log_truncate between 10.3 and 10.5.
Attachments
Issue Links
- relates to
-
MDEV-31373 innodb_undo_log_truncate=ON recovery results in a corrupted undo log
-
- Closed
-
-
MDEV-18976 Implement a CHECKSUM redo log record for improved validation
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
issue.field.resolutiondate | 2022-06-14 13:09:28.0 | 2022-06-14 13:09:28.149 |
Fix Version/s | 10.6.9 [ 27507 ] | |
Fix Version/s | 10.7.5 [ 27505 ] | |
Fix Version/s | 10.8.4 [ 27503 ] | |
Fix Version/s | 10.9.2 [ 27115 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Fix Version/s | 10.7 [ 24805 ] | |
Fix Version/s | 10.8 [ 26121 ] | |
Fix Version/s | 10.9 [ 26905 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue relates to |