We get an assertion failure because we do a find on the secondary which is not fully updated with the primary when running in the concurrency_sharded_causal_consistency_and_balancer suite.
Ban fsm_workloads/agg_sort.js in concurrency_sharded_causal_consistency_and_balancer
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: