Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- symbolized

Assigned Teams:

Storage Engines - Server Integration
Sprint:
SESISailing - 2025-12-09
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Existing replsetResizeOplog integration tests aren't sufficiently realistic to cover known use-cases (see e.g. AF-8304). Some important considerations:

Resizes on a live cluster (mid-replication)
Resizes on sharded setups
Resizes immediately following a restore of a large oplog (this is what happened in the linked AF

is related to

SERVER-113936 No test coverage for some FSM workloads directly against replica set with primary restarts

Open

SERVER-94787 Avoid abandoning the snapshot explicitly in CollectionScan

Closed

related to

SERVER-113938 Detect when tests aren't running in any suites

Backlog

split from

SERVER-113838 Allow concurrent oplog resize during async oplog sampling

Closed

Assignee:: Nic Hollingum
Reporter:: Nic Hollingum
Participants:: Nic Hollingum
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Nov 14 2025 03:47:48 AM UTC
Updated:: Nov 24 2025 02:50:30 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates