[SERVER-38916] Change the LinkBench test suite to test sharded collections Created: 09/Jan/19  Updated: 29/Oct/23  Resolved: 27/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-38917 Improve LinkBench schema to scale wel... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-04-08
Participants:

 Description   

Right now our LinkBench tests for sharded clusters only test the case where there's a single shard, and thus two-phase commit is not required. We need to also test the case where more than one shard is involved in transaction commit.



 Comments   
Comment by Githook User [ 27/Mar/19 ]

Author:

{'email': 'saltzm@gmail.com', 'name': 'Matthew Saltz', 'username': 'saltzm'}

Message: SERVER-38916 Modify linkbench to shard collections in a sharded cluster (#334)

  • SERVER-38916 Modify linkbench to shard collections in a sharded cluster
  • Make indexes unique
  • Use variable for maxid1, remove unique indexes from count and link collections
Generated at Thu Feb 08 04:50:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.