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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc1, 4.1.1
    • Component/s: None
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Storage NYC 2018-06-04
    • Linked BF Score:
      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

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: