[SERVER-40126] Catch MustDowngrade errors thrown by repairDatabaseAndCheckVersion Created: 14/Mar/19  Updated: 29/Oct/23  Resolved: 19/Mar/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1.10

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Divjot Arora (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-40022 Clarify Collection ownership and tran... Closed
Duplicate
is duplicated by SERVER-39916 v4.2 unclean shutdown during startup ... Closed
Related
is related to SERVER-40261 Remove special no-collection-uuid han... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-03-25
Participants:

 Description   

In db.cpp, the call to repairDatabaseAndCheckVersion only every returns a MustDowngrade error, which forces the server to exit cleanly. 

Lower levels the code, DatabaseHolder::openDb for example, may need to throw the MustDowngrade error code, so db.cpp::_initAndListen should be modified to catch this error and exit cleanly.



 Comments   
Comment by Githook User [ 19/Mar/19 ]

Author:

{'name': 'Divjot Arora', 'username': 'divjotarora', 'email': 'divjot.arora@10gen.com'}

Message: SERVER-40126 Change openDb to throw exception
Branch: master
https://github.com/mongodb/mongo/commit/c9288a60089bf421d51c7a8573a2ceb5849edfd8

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