[SERVER-36148] setFCV downgrade fails on long index namespaces Created: 16/Jul/18  Updated: 29/Oct/23  Resolved: 20/Jul/18

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: nyc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-36422 restartCatalog fails under FCV 4.0 in... Closed
is related to SERVER-35824 support for long index namespaces sho... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-07-30
Participants:
Linked BF Score: 6

 Description   

SERVER-35824 changed the setFCV downgrade logic to detect index namespaces that are incompatible with 4.0. The setFCV command would fail in the presence of these long index namespaces.

This downgrade check is not necessary because the startup validation logic in a 4.0 server would detect these invalid index namespaces and fail to start up. The user would still be able to fix the invalid namespaces using a 4.2 binary in 4.0 FCV mode.



 Comments   
Comment by Githook User [ 20/Jul/18 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-36148 allow downgrade to 4.0 in the presence of long index namespaces.

These long index namespaces will be detected at startup in a 4.0 server.

This reverts commit 6a7e25af6aeb1f612019c15c73258341a5779c16.
Branch: master
https://github.com/mongodb/mongo/commit/4cdaee88d7122f3ccba152ae37d3b5b69b3b398f

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