Loading...
Loading...
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
JIRAUSER1270794 commented on Tue, 6 Sep 2022 15:26:07 +0000: Hi aldo.bongio@servitly.com , Thanks for reporting the issue that occurred during downgrading. Please note that downgrading multiple major versions (e.g. 4.4 to 4.2 to 4.0) is not supported, thus any techniques that try to fulfill this use-case have no guarantee of working. Additionally, MongoDB version 4.0 reached the end of life in April 2022 and is no longer supported and our general guidance is to avoid downgrading to an unsupported version. Regards, Yuan
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
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.