[SERVER-35625] Remove 3.6-specific WiredTiger compatibility handling Created: 15/Jun/18  Updated: 29/Oct/23  Resolved: 18/Jun/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-35117 Enumerate and remove Storage-related ... Closed
is depended on by SERVER-35631 Storage-related generic upgrade/downg... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-06-18, Storage NYC 2018-07-02
Participants:

 Description   

The WiredTiger compatibility handling that was added as part of SERVER-32590 and was specific to 3.6 should be removed. Per the discussion in SERVER-35117, this includes the following:

For the purposes of unblocking this work, we should set compatibility=(require_min="3.1.0") to determine whether starting with FCV=4.0. References to earlier WT versions should be removed. Since compatibility is omitted to enable the latest behavior in WiredTiger, none of these changes need to wait for the WiredTiger version to be bumped.

When downgrading (to 4.0) as part of clean shutdown, if downgrading:

  • we should remove any use_timestamp configuration to WT_CONNECTION::close (the default behavior should be correct for 4.1 and above)
  • we should remove the loop that calls WiredTigerUtil::setTableLogging
  • we should not need to close / reopen and then close again.
  • Instead, it should be sufficient to call _conn->reconfigure with compatibility=(release=3.1) with just one call to _conn->close


 Comments   
Comment by Githook User [ 18/Jun/18 ]

Author:

{'username': 'mvankeulen94', 'name': 'Maria van Keulen', 'email': 'maria@mongodb.com'}

Message: SERVER-35625 Remove 3.6-specific WiredTiger file handling
Branch: master
https://github.com/mongodb/mongo/commit/013b82bf5f58bd7de8ae2f4d28d24f82afa22e64

Comment by Maria van Keulen [ 15/Jun/18 ]

Due to arbiter FCV semantics on 4.0, the WiredTiger files are downgraded to release compatibility 2.9 on clean shutdown. In order to allow arbiters to start up with 4.2 binaries, the WiredTiger compatibility check must accommodate 2.9.

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