[SERVER-37472] Improve behavior if user downgrades to 4.0 binary without setting FCV to 4.0 Created: 04/Oct/18 Updated: 29/Oct/23 Resolved: 02/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | 4.0.3 |
| Fix Version/s: | 4.0.5, 4.1.5 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Eric Milkie | Assignee: | Natalie Tsvetkova |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19 | ||||
| Participants: | |||||
| Description |
|
Currently, if a user tries to run a 4.0 mongod binary on data files from FCV 4.2, the following messages appear in the log:
|
| Comments |
| Comment by Githook User [ 13/Nov/18 ] | |
|
Author: {'name': 'natalie.tsvetkova', 'email': 'natalie.tsvetkova@mongodb.com', 'username': 'ntsvetko'}Message: (cherry picked from commit bda182eaab096c34f57efe94f5e0a8022c54bcc3) | |
| Comment by Githook User [ 31/Oct/18 ] | |
|
Author: {'name': 'natalie.tsvetkova', 'email': 'natalie.tsvetkova@mongodb.com', 'username': 'ntsvetko'}Message: | |
| Comment by Eric Milkie [ 05/Oct/18 ] | |
|
Something like that, yes. At the very minimum, we shouldn't print the message about having upgraded from prior to 3.6. | |
| Comment by Kaloian Manassiev [ 05/Oct/18 ] | |
|
milkie, the messaging improvement you have in mind here would be to make it say something like this, right:
|