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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.3, 3.5.2
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Repl 2017-02-13
    • Linked BF Score:
      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

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: