[SERVER-38435] Add concurrency workload for multi-writes (including _id broadcasts) in sharded transactions Created: 06/Dec/18 Updated: 29/Oct/23 Resolved: 01/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Task | 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 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11 |
| Participants: |
| Description |
|
The behavior of multi-writes is different in sharded transactions than outside them (they are versioned and not broadcast to all shards) so we add a concurrency workload to verify they work as expected. The workload should include _id updates and possibly manual moveChunks. |
| Comments |
| Comment by Githook User [ 05/Feb/19 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Githook User [ 01/Feb/19 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |