-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Verify
-
None
-
Storage Engines, Storage Engines - Foundations, Storage Engines - Persistence
-
None
-
8
Current understanding is that verification takes some global locks (like checkpoint and schema locks) that prevents other events like checkpoints and transactions from happening. That could have been fine in the past, but things change with DisAgg for many reasons. The one thing is making checkpoints more frequently, so it’s worth checking whether it’s still OK to lock checkpoints while the verification is in progress and whether we can do better and improve customer experience by changing the synchronization.
So the questions for this direction are:
- Is it OK to take checkpoint lock since it would prevent checkpoints from happening?
- Should we somehow allow transitions while doing the verification (maybe postpone verification)?
- Are there any other synchronizations happening for verification now that could be weakened for DisAgg?
Please check the corresponding doc section for more details.
- related to
-
WT-14911 Verify that the ingest table is always empty for primary
-
- Needs Scheduling
-