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

4.0 rc0 upgrade from 3.6.5 logs "unsupported WiredTiger file version" error

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.15, 4.0.0-rc6, 4.1.1
    • Affects Version/s: 4.0.0-rc0
    • Component/s: WiredTiger
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Hide

      1. Create a standalone MongoDB 3.4.15 instance.
      2. Upgrade to MongoDB 3.6.5 by starting new binaries.
      3. Set FCV to "3.6".
      4. Upgrade to MongoDB 4.0.0 rc0 by starting new binaries.
      5. Examine the mongod log file for the unsupported WT file version error.

      Show
      1. Create a standalone MongoDB 3.4.15 instance. 2. Upgrade to MongoDB 3.6.5 by starting new binaries. 3. Set FCV to "3.6". 4. Upgrade to MongoDB 4.0.0 rc0 by starting new binaries. 5. Examine the mongod log file for the unsupported WT file version error.
    • Storage NYC 2018-06-04, Storage NYC 2018-06-18
    • 63

      Created a MongoDB 3.4.15 standalone, then upgraded to 3.6.5, set FCV to "3.6", then upgraded to 4.0.0 rc0. See a message in the log file:

      2018-05-29T12:15:43.124-0500 E STORAGE  [initandlisten] WiredTiger error (-31802) [1527614143:124208][2993:0x7fffddf7a3c0], connection: unsupported WiredTiger file version: this build requires a minimum version of 3, and the file is version 2: WT_ERROR: non-specific WiredTiger error

      but, things seem to be working.

      If WT file version 2 is supported in 4.0, this message should be a warning at most.

      Also, how would one go about converting to version 3, if there is a reason to do so?

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            spencer.brown@mongodb.com Spencer Brown
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: