[SERVER-32590] RTT 3.6<->4.0 upgrade/downgrade. Created: 08/Jan/18  Updated: 30/Oct/23  Resolved: 18/May/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng, rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on WT-3906 Respect stable_timestamp in WT_CONNEC... Closed
depends on WT-4056 New API to configure a minimum compat... Closed
Duplicate
is duplicated by SERVER-30667 Recover to a Timestamp Up/Down Testin... Closed
is duplicated by SERVER-30668 Recover To A Timestamp Up/Down Testin... Closed
Gantt End to End
has to be finished together with WT-4029 Bump the log file version Closed
Related
related to SERVER-34630 Change WiredTiger compatibility versi... Closed
related to WT-3387 Add support for a stable timestamp Closed
is related to SERVER-40954 Error message for UnrecoverableRollba... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-02-12, Repl 2018-03-12, Repl 2018-03-26, Repl 2018-04-09, Storage NYC 2018-05-21
Participants:
Case:

 Description   

On clean shutdown when in FCV 3.6 a 4.0 binary must:

  • Set the WT "recovery timestamp" to 0
  • Take an unstable checkpoint
  • Enable WT logging for all tables

Additionally, a 4.0 binary running in FCV 3.6 should persist some state such that a 3.6 binary cannot startup on the datafiles following a crash.



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

Author:

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

Message: SERVER-32590: WT 3.6 <-> 4.0 upgrade/downgrade.
Branch: master
https://github.com/mongodb/mongo/commit/180e9e548df8261a919000aa68b9419b9df093f2

Comment by Daniel Gottlieb (Inactive) [ 12/Apr/18 ]

With WT-3959, the original intention of this ticket is accomplished; the recovery timestamp will be set to 0 when the checkpoint at shutdown is taken with `use_timestamp=false`.

I'm repurposing this ticket for changing the log file version back down to the 3.6 compatible version when the server performs a clean shutdown with FCV 3.6. This depends on WT-4029.

Comment by Daniel Gottlieb (Inactive) [ 02/Feb/18 ]

I think the way to do this is to unset the stable_timestamp before closing the connection. Some discussion was on the original WT-3387 ticket.

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