[SERVER-49018] v4.4 FCV downgrade must check that no recordPreImages flag is set on any collection Created: 22/Jun/20  Updated: 06/Dec/22  Resolved: 17/Sep/20

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: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to SERVER-48971 collMod in v4.4 cannot accept the new... Closed
is related to SERVER-49366 Standalone node cannot startup with '... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Currently on v4.4, a v4.4 FCV 4.4 node can

  • set recordPreImages on a collection
  • downgrade FCV from 4.4 to 4.2
  • shutdown and restart, in FCV 4.2, and find that recordPreImages is set on a collection, which crashes the node on startup.
    We shouldn't have any possible crashing behavior. And I'm not sure there's a recovery path, unless v4.2 binaries ignore unknown fields in collection options.

There is a test that showcases this FCV 4.2 crashing on startup behavior.

The setFeatureCompatibilityVersion command has hooks for FCV downgrade and upgrade checks and changes. A hook should be added to the downgrade code to check that the recordPreImages flag is not set on any collection.

Alternatively, the flag could be unset on downgrade, but I'm not familiar with the feature repercussions that might cause.


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