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

Delete oplogFetcherUsesExhaust server parameter if running last-stable binary

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.4
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-03-09
    • 36

    Description

      When starting a replica set, we re-use the options for all the nodes. For multiversion replica sets, this means that if a node set the oplogFetcherUsesExhaust server parameter to false, if we don't reset or delete the parameter, the next node will inherit that parameter. If the next node is running 4.2, this means that it will try to set the parameter, but fail because it doesn't know about it.

      We should delete the parameter in all cases when running with a last-stable bin version to be safe.

      Attachments

        Activity

          People

            samy.lanka@mongodb.com Samyukta Lanka
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: