The two update_upsert_multi.js concurrency workloads are blacklisted from all sharded suites because they perform multi updates without the shard key. The updates from all workloads do include the thread id, so if the collections used by each workload is sharded by thread id instead of defaulting to _id, both workloads should be able to run against sharded clusters.
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: