Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36674

Impact on unrelated shard workload

    • Service Arch
    • 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

      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.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            mira.carey@mongodb.com Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: