We should await replication on the config server after shardCollection is called because we read from the nearest config when refreshing, and can potentially read stale metadata.
Await replication on config server after shardCollection in safe secondary reads tests
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: