-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-02-02, Storage Execution 2026-03-02
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The existing validate hook(s) need to be updated to check for replicated fastcounts after all tests.
- Background validation that runs during some jstests. Does it need to be updated? Does it still work?
- The resmoke validate hook is here and here.
- Other references to hard-coding enforcement of fastcount exist (like here and here), consider what needs to be updated now or later on during development of replicated fastcounts.
Validate needs to detect which fastcount system exists, and perform the correct validation of fastcount. Since this is run widely in evergreen, basic detection logic must be correct for patch builds to pass.
Success of this ticket means the basic replicated fastcount is validating correctly regardless of feature flag state or DSC/ASC.
- depends on
-
SERVER-117575 Address circular dependency between metadata_manager and shard_role
-
- Closed
-
- is related to
-
SERVER-104258 Resharding Can Hang If Recipient Fails During ShardsvrReshardRecipientClone
-
- Closed
-
-
SERVER-104494 Resharding can hang if recipient steps down during ShardsvrReshardRecipientClone
-
- Closed
-
-
SERVER-117454 Enable replicated collection size and count in all feature flag builds
-
- Open
-
-
SERVER-117924 Re-enable all-feature-flag variant test coverage
-
- Backlog
-
-
SERVER-118531 Test FastCountType validation on both DSC and ASC
-
- Closed
-