[SERVER-44247] Rename index 'ns' fields on renameCollection when in FCV4.2 Created: 25/Oct/19  Updated: 29/Oct/23  Resolved: 03/Dec/19

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

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-12-02, Execution Team 2019-12-16
Participants:
Linked BF Score: 50

 Description   

SERVER-41696 removes the 'ns' field from indexes in 4.4 upgrade and SERVER-41697 removed the logic from the latest mongod binary completely for renaming the 'ns' field of the index. We should continue to rename the 'ns' field of the index when on FCV4.2 or we can fail to startup on downgrade due to this fassert during startup recovery.

Steps to reproduce:
1. Create a collection db_one on a 4.2 mongod binary

2 Restart using master binary on FCV4.2 and rename a collection from db_one to db_two

  • The 'ns' field of the index will not be renamed

3. restart again as a 4.2 binary

  • On startup, we fail to validate the index because the collection name 'db_two' does not match the index 'ns' field 'db_one'


 Comments   
Comment by Githook User [ 03/Dec/19 ]

Author:

{'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}

Message: SERVER-44247 Rename index 'ns' fields when renaming collections in FCV 4.2
Branch: master
https://github.com/mongodb/mongo/commit/39e338fe6fa2205c4321fb447e263f4ba42b5ce1

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