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

Reduce replication lag when primary is overloaded

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication, Storage
    • Labels:

      Description

      Reproducible deterministically. After a bit the load is run on the primary rs.status() will report optimeDate on any of the secondary being far behind the one of the primary. Can be reproduced even with a 3-members replica set all in the same availability zone, in an AWS datacenter.

      Get linkbench from https://github.com/dcci/linkbench and run

      ./bin/linkbench -c config/LinkConfigMongoDb.properties -l

      Relevant configuration bits into LinkConfigMongodb.properties

      loaders = 3

      or higher

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              davide.italiano Davide Italiano
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: