[SERVER-36674] Impact on unrelated shard workload Created: 14/Aug/18  Updated: 23/Mar/23  Resolved: 02/Nov/21

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

Type: Task Priority: Major - P3
Reporter: Mira Carey Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 0
Labels: PM-1211, re-triaged-ticket
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Sprint: Service Arch 2018-10-08, Service Arch 2018-10-22, Service Arch 2018-11-05, Service Arch 2018-11-19, Service Arch 2018-12-03
Participants:

 Description   

What happens to work for other shards, while you cannot target one shard

Test:

  • Set up a two shard cluster
  • Run a load of N requests per second that hit each shard through one mongos
  • Do a thing:
    • SIGSTOP one shardsvr
    • Trigger an election
  • Measure the degradation in throughput and latency for operations that target the other shard. Less than 10% is a decent first target.  Ideally there should be 0 degradation.


 Comments   
Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ]

The Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable.

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