[SERVER-39916] v4.2 unclean shutdown during startup on v3.2 binary files prevents starting up a v3.2 binary again Created: 01/Mar/19  Updated: 21/Mar/19  Resolved: 21/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Divjot Arora (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-40126 Catch MustDowngrade errors thrown by ... Closed
Related
related to SERVER-39861 Add collection UUID to log messages a... Closed
Sprint: Storage NYC 2019-03-25
Participants:
Linked BF Score: 0

 Description   

From conversation:

"Dan says this problem can happen if you do an unclean shutdown instead of clean, in the new version
because clean shutdown sets the WT wire version back to the original one for you.
need to call exitCleanly() in order to downgrade back to the original version"



 Comments   
Comment by Divjot Arora (Inactive) [ 21/Mar/19 ]

SERVER-40126 fixed the issue of shutting down uncleanly if a collection without UUIDs is not found. The current code in master throws a MustDowngrade exception if a collection does not have a UUID, which always results in a clean shutdown.

Comment by Divjot Arora (Inactive) [ 19/Mar/19 ]

Possibly a duplicate of SERVER-40126.

Comment by Sara Williamson [ 07/Mar/19 ]

If UUIDs are missing, we need to exit cleanly.

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