Dowgrade 4.4 -> 4.2 -> 4.0 not working

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.4.15
    • Component/s: None
    • None
    • ALL
    • Hide

      This script based on MongoDB on Docker reproduces the issue.

      In summary:

      1. The upgrade 4.0.28 -> 4.2.21 works
      2. The upgrade 4.2.21 -> 4.4.15 works
      3. The downgrade 4.4.15 -> 4.2.21 works
      4. After the downgrade 4.2.21 -> 4.0.28 MongoDB refuses to start with the reported error.

      The script can be easily adapted to different paths, you just have to adjust versions and fcv. I successfully tried the following paths:

      • 3.2.21 -> 3.4.24 > 3.6.23 -> 3.4.24 -> 3.2.21
      • 3.4.24 > 3.6.23 -> 4.0.28 -> 3.6.23 -> 3.4.24
      • 3.6.23 -> 4.0.28 -> 4.2.21 -> 4.0.28 -> 3.6.23

      I've read https://jira.mongodb.org/browse/SERVER-55313 and its 2nd comment, but it doesn't seem my case (please correct me if I'm wrong):

      • I'm downgrading from version 4.4.15 to 4.2.21 so I'm not hitting the downgrade floor reported here
      • And then I'm downgrading from version 4.2.21 to 4.0.28 according to the downgrade guide here
      Show
      This script based on MongoDB on Docker reproduces the issue. In summary: The upgrade 4.0.28 -> 4.2.21 works The upgrade 4.2.21 -> 4.4.15 works The downgrade 4.4.15 -> 4.2.21 works After the downgrade 4.2.21 -> 4.0.28 MongoDB refuses to start with the reported error. The script can be easily adapted to different paths, you just have to adjust versions and fcv. I successfully tried the following paths: 3.2.21 -> 3.4.24 > 3.6.23 -> 3.4.24 -> 3.2.21 3.4.24 > 3.6.23 -> 4.0.28 -> 3.6.23 -> 3.4.24 3.6.23 -> 4.0.28 -> 4.2.21 -> 4.0.28 -> 3.6.23 I've read https://jira.mongodb.org/browse/SERVER-55313 and its 2nd comment, but it doesn't seem my case (please correct me if I'm wrong): I'm downgrading from version 4.4.15 to 4.2.21 so I'm not hitting the downgrade floor reported here And then I'm downgrading from version 4.2.21 to 4.0.28 according to the downgrade guide here
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Performing an upgrade 4.0 -> 4.2 -> 4.4 works. Trying to revert to 4.0 produces the following error when the 4.0 starts:

      2022-09-01T09:06:59.754+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1662023219:754789][1:0x7f3032233a80], connection: __log_open_verify, 985: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error Raw: [1662023219:754789][1:0x7f3032233a80], connection: __log_open_verify, 985: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error
2022-09-01T09:06:59.762+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1662023219:762298][1:0x7f3032233a80], connection: __log_open_verify, 985: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error Raw: [1662023219:762298][1:0x7f3032233a80], connection: __log_open_verify, 985: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error
2022-09-01T09:06:59.767+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1662023219:767941][1:0x7f3032233a80], connection: __log_open_verify, 985: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error Raw: [1662023219:767941][1:0x7f3032233a80], connection: __log_open_verify, 985: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error
2022-09-01T09:06:59.769+0000 W STORAGE  [initandlisten] Failed to start up WiredTiger under any compatibility version.
2022-09-01T09:06:59.769+0000 F STORAGE  [initandlisten] Reason: -31802: WT_ERROR: non-specific WiredTiger error
2022-09-01T09:06:59.769+0000 F -        [initandlisten] Fatal Assertion 28595 at src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 711
2022-09-01T09:06:59.769+0000 F -        [initandlisten] \n\n***aborting after fassert() failure\n\n

            Assignee:
            Yuan Fang
            Reporter:
            Aldo Bongio
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: