slaveDelay Setting Causes Replica Ops to be Applied in Batches at approximately the slaveDelay Interval

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.2.1, 2.3.0
    • Affects Version/s: 2.2.0-rc0
    • Component/s: Replication
    • None
    • Environment:
      Linux, 2.2.0-rc0 - Sharded, 11 clusters
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a slave delay is specified ("slaveDelay": 7200 in the original case), the replication ops are applied in batches at approximately the 7200 second interval. As a result, there are massive write spikes (insert/updates), lock percentage spikes, disk IO spikes and DR102 errors caused

        1. delay.js
          1 kB
          Randolph Tan
        2. load_gen.js
          0.1 kB
          Randolph Tan

            Assignee:
            Randolph Tan
            Reporter:
            Adam Comerford
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: