-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2024-10-28
-
0
Some test cases check the write concern error context is properly passed through. A replication stall is forced to exercise this path. However, if there was a filtering metadata refresh ongoing, the wc failure might be due to the SSCCL noop write, instead of the "user write" wait for write concern, e.g. wait for replicating a createIndexes.
- is related to
-
SERVER-96033 Investigate ShardServerCatalogCacheLoader surfacing write concern error
- Closed
-
SERVER-97590 mongos_unsharded_commands_interface_parity_with_replica_set.js not correctly accessing 'global' field to fetch filtering metadata status
- Closed