[SERVER-21051] Add a suite that runs existing sharding tests while probabilistically dropping messages within the CSRS Created: 21/Oct/15  Updated: 06/Dec/22  Resolved: 12/Dec/16

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-22563 Establishing remote cursor during rol... Closed
depends on SERVER-20982 Add concurrency workload framework to... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Sprint: Sharding B (10/30/15), Sharding C (11/20/15), Sharding D (12/11/15), Sharding E (01/08/16), Sharding F (01/29/16), Sharding 10 (02/19/16), Sharding 11 (03/11/16)
Participants:

 Comments   
Comment by Esha Maharishi (Inactive) [ 02/Feb/16 ]

code review: https://mongodbcr.appspot.com/42810001/

Comment by Spencer Brody (Inactive) [ 27/Jan/16 ]

I think the best way to implement this ticket would be to create a new suite in MCI that runs the existing sharding suite, but with the config servers set up with mongobridge to drop packets X% of the time (where X is probably somewhere around 5-10). This should cause some failovers and other operation failures, but most should be transparently retried.

Generated at Thu Feb 08 03:56:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.