[SERVER-19498] CatalogManagerReplicaSet does not respect the "excluding" field in the config.version document Created: 20/Jul/15  Updated: 21/Jul/15  Resolved: 21/Jul/15

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-19329 RS Catalog Manager Implementation for... Closed
is related to SERVER-19512 Remove jstests/multiVersion/config_ve... Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Sprint: Sharding 7 08/10/15
Participants:

 Description   

It is possible to write an "excluding" field to the config.version document with explicit mongodb bin versions to not allow. We are not checking that field in the new catalog manager's upgrade path.



 Comments   
Comment by Spencer Brody (Inactive) [ 21/Jul/15 ]

This functionality was never documents or publicized as a user feature, and in fact we explicitly caution against modifying config.version manually. Since it isn't used internally anywhere, there is no reason to keep the functionality around. Therefore we are not porting this functionality to the new replica set catalog manager, essentially removing this feature from 3.2 and future versions.

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