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

apply setParameter for maxSyncSourceLagSecs to slave 2 only in maxSyncSourceLagSecs.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.3, 3.5.2
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-02-13
    • 0

    Description

      We can stabilize the test by selectively apply change maxSyncSourceLagSecs on slave 2 only instead of both slaves 1 and 2.

      ---- update —
      maxSyncSourceLagSecs.js changes how the secondaries sync from one another. It is appropriate to use the fail point introduced in SERVER-27231 to stabilize the test.

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: