-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines - Server Integration
-
SESINic(k)less - 2026-06-16, SESINEXT 2026-07-28
-
None
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-124309 adds more startup tests for us . However, as we increase the number of collections, we face more standby lag that causes the test to occasionally fail due to timeouts. We should tweak the test structure so that we can try avoid this. Since the standby lag exists in the creation of the collections, one solution could be to create the collections with just the primary, then startup the standby to read from the latest checkpoint instead of having to apply the oplog one by one. We should also investigate if we can just shut down the standby altogether, and only restart our singular node, so we can avoid the issue of the standby lag.
Here are some runs with the creation startup, with varying success.
- is blocked by
-
WT-17791 Optimise direct ingest creation to mitigate core startup bottlenecks
-
- Closed
-
- is related to
-
SERVER-130386 Try disagg measure startup tasks with retry on crash
-
- Open
-
-
SERVER-130385 Prepare disagg startup DSI test for more collections
-
- In Code Review
-