[SERVER-69354] Dowgrade 4.4 -> 4.2 -> 4.0 not working Created: 01/Sep/22  Updated: 27/Oct/23  Resolved: 07/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.15
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Aldo Bongio Assignee: Yuan Fang
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-71635 MongoDB4.2.23 can not downgrade to 4.... Closed
Related
Operating System: ALL
Steps To Reproduce:

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
Participants:

 Description   

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 



 Comments   
Comment by Yuan Fang [ 06/Sep/22 ]

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

Generated at Thu Feb 08 06:13:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.