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

Change WiredTiger compatibility version setting in 3.6 release

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Storage Non-NYC 2018-05-07, Storage NYC 2018-05-21

    Description

      We are introducing a log format version change in the 4.0 release, as part of recoverable rollback work. The change is being made in WT-4029.

      We should update MongoDB to pass compatibility=(release=3.0) when it calls wiredtiger_open, so that users who open a database that has been used by MongoDB 4.0 and has not had a clean shutdown get a useful error message.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35271 4.0 rc0 upgrade from 3.6.5 logs "unsupported WiredTiger file version" error

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. WT-4098 Add new compatibility_max configuration option

          • Major - P3 - Major loss of function.
          • Closed
          has to be finished together with

          Improvement - An improvement or enhancement to an existing feature or task. WT-4122 Ensure compatibility downgrade cleans up old log files

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-32590 RTT 3.6<->4.0 upgrade/downgrade.

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. WT-4029 Bump the log file version

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35572 Always allow log archiving in WiredTiger

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              alexander.gorrod@mongodb.com Alexander Gorrod
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: