[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: SERVER-38979 Shard by thread id in update_upsert_multi fsm workloads
Branch: master
https://github.com/mongodb/mongo/commit/9d78b85155127d5b82a216e634ba7ee0c7c5d87d

Generated at Thu Feb 08 04:50:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.