-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Schema Management, Test Csuite
-
Storage Engines - Foundations
-
665.517
-
None
-
3
In the schema-disagg-abort test all schema operations (create and drop) issued their corresponding publish calls before the step_down_timestamp is set.
It looks like a leftover from the early days of schema epoch implementation. There is no reason to issue all outstanding publish events before step-down starts.
TODO:
- Investigate that publish (for create and drop) can be called after step_down_timestamp is set. Establish correct timestamp for this publish.
- Do not flush pending publish events before step-down starts. Let the publish events flow naturally across step-down.
- is blocked by
-
WT-18284 Ensure correct handling of CREATE/DROP/CREATE patterns
-
- Backlog
-
-
WT-18272 Validate a pending DROP before panicking on skipped shared metadata creates
-
- In Code Review
-
- is related to
-
WT-18360 Checkpoint pickup attaches a dropped incarnation's stable constituent to a recreated layered table
-
- Closed
-
- related to
-
WT-18258 Run operations during async step-down window
-
- Closed
-