-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
Fully Compatible
-
Repl 2018-02-12, Repl 2018-03-12, Repl 2018-03-26, Repl 2018-04-09, Storage NYC 2018-05-21
-
(copied to CRM)
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.
- depends on
-
WT-3906 Respect stable_timestamp in WT_CONNECTION::close
- Closed
-
WT-4056 New API to configure a minimum compatibility version on open
- Closed
- has to be finished together with
-
WT-4029 Bump the log file version
- Closed
- is duplicated by
-
SERVER-30667 Recover to a Timestamp Up/Down Testing: Successful Upgrade/Downgrade Scenario
- Closed
-
SERVER-30668 Recover To A Timestamp Up/Down Testing: Unclean Downgrade Attempt
- Closed
- is related to
-
SERVER-40954 Error message for UnrecoverableRollbackError in FCV 3.6 should recommend downgrading to 3.6
- Closed
- related to
-
SERVER-34630 Change WiredTiger compatibility version setting in 3.6 release
- Closed
-
WT-3387 Add support for a stable timestamp
- Closed