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

Reduce replication lag when primary is overloaded

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication, Storage
    • Replication

    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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: