[SERVER-36673] Secondary Allowed Workload Created: 14/Aug/18  Updated: 06/Dec/22

Status: Backlog
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: Unresolved Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
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   

Test:

  • Set up a 3 node replica set
  • Run a load of N secondaryPreferred (or nearest) requests per second
  • Try things:
    • SIGSTOP a node
    • Bring a secondary back online with a cold cache
    • Trigger an election (see what happens to the newly elected primary, how long does the work take to fall off it)
  • What happens when:
    • Elections happen
    • Secondaries are removed
    • Secondaries are added (cold)
  • What happens with secondary work


 Comments   
Comment by Jonathan Ma [ 02/Nov/21 ]

blake.oler  I think the implementation is complete, but not sure if it ever got added to the testing framework

Comment by Blake Oler [ 02/Nov/21 ]

jonathan.ma is this ticket done? Hasn't been updated for a few years, unsure what work we would need to do here.

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