[SERVER-47228] Enable the random moveChunk update shard key workload to run on the concurrency_sharded_with_stepdowns suite Created: 01/Apr/20  Updated: 06/Dec/22  Resolved: 16/Apr/20

Status: Closed
Project: Core Server
Component/s: Concurrency, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding
Participants:
Linked BF Score: 21

 Description   

Steps required:

  1. Make the verifyDocuments state function not create a cursor by projecting out everything but the _id and using a large batch size.
  2. Remove the "requires_non_retryable_writes" tag


 Comments   
Comment by Blake Oler [ 03/Apr/20 ]

This isn't a need-to-have, but would have been nice in order to see the linked BF a year earlier. Not super necessary now that Max enabled the test to run on other stepdown suites.

Generated at Thu Feb 08 05:13:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.