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

Halt replication on last-stable secondary before FCV upgrade on latest binary primary in set_feature_compatibility_version.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.0-rc1, 4.1.1
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-06-04
    • 11

    Description

      We've opted to close SERVER-33517 as won't fix, which means the test exercising the scenario must be modified so that it no longer fails.

      feature_compatibility_version_lagging_secondary.js avoids this problem by halting secondary replication while setFCV is called on the primary. I suspect it's only necessary to stop replication around the setFCV call. If so, perhaps modify feature_compatibility_version_lagging_secondary.js to do that, too, and add comments about why replication must stop!

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: