Reduce replication lag when primary is overloaded

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Davide Italiano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: