Failed to copy dymainc metadata
General
Escalation
General
Escalation
Description
Environment
None
Attachments
1
- 08 Sep 2022, 10:12 AM
Smart Checklist
Activity
Show:
Satya Bodapati February 27, 2023 at 8:09 PM
Other tests that fail with same assertion:
t/bug1002688.sh
t/bug1062684.sh (from (empty))
t/bug932623.sh
t/bug759701.sh
t/bug1022562.sh
It will good to get these tests fixed
Satya Bodapati February 27, 2023 at 8:01 PM
I verified that checkpoint_lsn doesn't move with the above patch (patch to reproduce crash).
Rahul Malik October 31, 2022 at 10:41 AM
Final prepare should only be done without apply-log-only.
Do not allow final prepare if backup is already prepared without apply-log-only.
Details
Details
Assignee
Rahul Malik
Rahul Malik(Deactivated)Reporter
Rahul Malik
Rahul Malik(Deactivated)Labels
Needs QA
Yes
Affects versions
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created September 8, 2022 at 10:10 AM
Updated June 7, 2024 at 3:43 PM
We have the logic of skipping dynamic metadata on the apply-log phase and relying on MySQL.ibd to copy those changes. see https://perconadev.atlassian.net/browse/PXB-2180#icft=PXB-2180
The issue comes if there are change that are not flushed to mysql.ibd before the incremental backup.
Incremental prepare will skip applying of DYNAMIC_METADATA redo and mysql.ibd will not have those changes.
How to reproduce
execute bug1028949.sh with the attached patch
.