-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2026-07-20, Storage Execution 2026-08-03
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Even with sizeStorer already disabled, the size and count changes are still tracked in memory. The values returned are simply incorrect. We should skip the legacy in-memory tracking when persistence provider uses replicated size and count.
- related to
-
SERVER-131883 Fix restart case in oplog_truncation_size_based.js
-
- Closed
-