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

Improve behavior if user downgrades to 4.0 binary without setting FCV to 4.0

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • 4.0.3
    • 4.0.5, 4.1.5
    • Upgrade/Downgrade
    • Fully Compatible
    • v4.0
    • Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19

    Description

      Currently, if a user tries to run a 4.0 mongod binary on data files from FCV 4.2, the following messages appear in the log:

      2018-10-04T08:40:21.447-0400 F STORAGE  [initandlisten] BadValue: Invalid value for version, found 4.2, expected '4.0' or '3.6'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "4.2" }. See http://dochub.mongodb.org/core/4.0-feature-compatibility.
      2018-10-04T08:40:21.447-0400 F CONTROL  [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: Unable to parse the featureCompatibilityVersion document. The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0. If you are upgrading to 4.0, see http://dochub.mongodb.org/core/4.0-upgrade-fcv.
      

      Attachments

        Activity

          People

            natalie.tsvetkova@mongodb.com Natalie Tsvetkova
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: