[SERVER-34630] Change WiredTiger compatibility version setting in 3.6 release Created: 24/Apr/18 Updated: 29/Oct/23 Resolved: 18/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alexander Gorrod | Assignee: | Alexander Gorrod |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SWNA, nonnyc, storage-engines | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||
| Sprint: | Storage Non-NYC 2018-05-07, Storage NYC 2018-05-21 | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||
| Description |
|
We are introducing a log format version change in the 4.0 release, as part of recoverable rollback work. The change is being made in We should update MongoDB to pass compatibility=(release=3.0) when it calls wiredtiger_open, so that users who open a database that has been used by MongoDB 4.0 and has not had a clean shutdown get a useful error message. |
| Comments |
| Comment by Githook User [ 18/Jun/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {'username': 'dgottlieb', 'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Gorrod [ 18/Jun/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
The expected server change here is:
Note: I edited this to remove the patch sepcification in the versions. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Gorrod [ 24/May/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
michael.cahill I believe you are right. I've opened | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Michael Cahill (Inactive) [ 17/May/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
alexander.gorrod, is the change proposed here (together with Is there an additional constraint that to keep WT's mongodb-3.6 branch in sync with develop, we'll need a way to force startup to fail if the files on disk are too new? In other words, do we need require_max as well as require_min? | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 10/May/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
I might be missing the intent behind the "Upgraded/Downgraded" column, but omitting that results in the same WiredTiger log version, so I presume it's a benign addition. Regardless, the resulting WT log versions are correct. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Gorrod [ 09/May/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
The WiredTiger side of this work is done and staged - our testing indicates that this needs more careful co-ordination than expected to avoid introducing automated test regressions. When running the do_upgrade_downgrade.js multiversion test, it fails if we include the WiredTiger log file version change with:
Which i believe is the expected failure mode. My understanding is that the following MongoDB configurations should match with WiredTiger log format versions after clean shutdown:
daniel.gottlieb Could you confirm that the above is what you expect, and setup changes so that the correct WiredTiger versions are configured for the different MongoDB versions and configurations? luke.chen We'll need to hold off pulling the changes for | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Gorrod [ 24/Apr/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
donald.anderson Would you mind picking this change up? It doesn't need to happen after milkie The fix version on this ticket is a bit strange - this change is targeted at the 3.6 release, but should be made prior to 4.0 being cut. Feel free to adjust the ticket setup to reflect that intended state of affairs. |