[SERVER-36507] Downgrading WT from FCV 4.2 -> 4.0 requires an "acquiesced" system Created: 07/Aug/18  Updated: 29/Oct/23  Resolved: 27/Dec/18

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: nyc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-12-31
Participants:
Linked BF Score: 54
Story Points: 1

 Description   

The 4.0 -> 3.6 FCV downgrade path in storage would acquiesce the system by closing/re-opening the WT connection. That was originally done to facilitate changing table logging settings.

4.2 development optimistically removed the close/open along with the table logging changes under the assumption that changing the file compatibility on reconfigure (which remains in the upgrade/downgrade path) did not need to be acquiesced to the same degree.



 Comments   
Comment by Githook User [ 27/Dec/18 ]

Author:

{'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb'}

Message: SERVER-36507: Clean WT state before performing a reconfigure for downgrade.
Branch: master
https://github.com/mongodb/mongo/commit/e9ab3a4f84e51e30e95c8e0c8f9ae46237e1a926

Generated at Thu Feb 08 04:43:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.