[SERVER-63898] Validate FCV downgrades don't affect existing clustered collections Created: 23/Feb/22  Updated: 29/Oct/23  Resolved: 23/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.3
Sprint: Execution Team 2022-03-21, Execution Team 2022-04-04
Participants:

 Description   

In the clustered_collection.js multiversion test we assert that 5.0 and last-continuous (5.2) nodes can't start up with clustered collections present, but the error is not helpful:

[js_test:clustered_collection] d20271| 2022-02-22T21:10:20.007+00:00 E  CONTROL  20557   [initandlisten] "DBException in initAndListen, terminating","attr":{"error":"BadValue: 'clusteredIndex' has to be a boolean."}

This is intended, but we must verify that existing clustered collections are not affected if we downgrade the FCV version of an already running cluster with clustered collections present.



 Comments   
Comment by Jordi Olivares Provencio [ 23/Mar/22 ]

Final implementation consists of validating that an FCV downgrade won't affect the already existing clustered collections.

Comment by Githook User [ 23/Mar/22 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-63898 Validate FCV downgrades won't affect existing clustered collections
Branch: master
https://github.com/mongodb/mongo/commit/c3fee8287bf070e1fa6309513a4e6d8100c440ee

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