-
Type:
Sub-task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2026-05-11, Storage Execution 2026-05-25, Storage Execution 2026-06-08, Storage Execution 2026-06-22, Storage Execution 2026-07-06, Storage Execution 2026-07-20, Storage Execution 2026-08-03, Storage Execution 2026-08-17, Storage Execution 2026-08-31, Storage Execution 2026-09-14, Storage Execution 2026-09-28, Storage Execution 2026-10-12, Storage Execution 2026-10-26
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In ASC sharded clusters, each shard is created with lastFCV and the collection config.user_writes_critical_sections is written to before the shard is added to the cluster and set to the latest fcv. This leaves some writes untracked in-memory before replicated size and count is enabled.
To make the sharding tests work with the feature in ASC, we can first exclude the special sharding collection config.user_writes_critical_sections from replicated size and count system and keep using legacy sizeStorer for it.