[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: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
On clean shutdown when in FCV 3.6 a 4.0 binary must:
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: |
| Comment by Daniel Gottlieb (Inactive) [ 12/Apr/18 ] |
|
With 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 |
| 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 |