[SERVER-19329] RS Catalog Manager Implementation for config upgrade Created: 08/Jul/15  Updated: 02/Aug/18  Resolved: 14/Jul/15

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

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-19151 Implement config upgrade for replica ... Closed
Related
is related to SERVER-19498 CatalogManagerReplicaSet does not res... Closed
is related to SERVER-19592 Remove config version increment from ... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Comments   
Comment by Andy Schwerin [ 22/Jul/15 ]

+1

On Tue, Jul 21, 2015, 6:10 PM Spencer T Brody (JIRA) <jira@mongodb.org>

Comment by Githook User [ 15/Jul/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-19272 SERVER-19329 VersionType should do validation properly and store MongoVersionRanges
Branch: master
https://github.com/mongodb/mongo/commit/27741287182d51ab3e79ff9dde42c21b754eb718

Comment by Githook User [ 13/Jul/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-19329 RS Catalog Manager Implementation for config upgrade

Only for v3.2:
When starting mongos with config servers as replica sets, only 2 config server states are allowed:

1. Blank slate.
2. Already upgraded to config version v7 (by passing --upgrade to v3.2 mongos running with old style config servers).
Branch: master
https://github.com/mongodb/mongo/commit/a23c7a22a838f91112bcc273654c9606331a9114

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