[SERVER-62953] Correctly record when the collection was explicitly clustered or not Created: 25/Jan/22  Updated: 29/Oct/23  Resolved: 02/Feb/22

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

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

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-02-07
Participants:

 Description   

Currently the code that checks whether the collection is clustered or not does not store the case where the user explicitly disabled clustering. Instead it's left unassigned and relies on default behaviour.

This might pose issues if nodes in one version of the database cluster a collection by default while others don't.



 Comments   
Comment by Githook User [ 02/Feb/22 ]

Author:

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

Message: SERVER-62953 Explicitly disable clustering when commanded by the user
Branch: master
https://github.com/mongodb/mongo/commit/cb6654f0251852820a0c4af4901f31fe21597377

Comment by Louis Williams [ 25/Jan/22 ]

We should do the minimal amount of work to ensure thatĀ if clustering is enabled by default in a future version, collections that explicitly disable clustering, can safely downgrade to 6.0.

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