[SERVER-38979] Shard by thread id in update_upsert_multi fsm workloads Created: 14/Jan/19 Updated: 29/Oct/23 Resolved: 15/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-01-28 |
| Participants: |
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 15/Jan/19 ] |
|
Author: {'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}Message: |