[SERVER-36675] maintenance in mongos 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 when we bounce / bring on a new mongos

Test:

  • Set up a 1 shard cluster
  • Set up a workload of N sleeps per second via a mongos
    • Stage these out so that the workload practically requires M connections to execute (due to the sleeps)
  • Measure steady state perf
  • Try stuff:
    • Set up a second mongos
      • Point an equivalent workload against it
    • Bounce the mongos
      • Time to reversion to mean
  • Variants:
    • Is it worse if there is a very large routing table
      • Many shards
      • Many chunks


 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:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.