[SERVER-25155] Create setFeatureCompatibilityVersion command Created: 19/Jul/16  Updated: 14/Mar/17  Resolved: 22/Aug/16

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

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on TOOLS-1371 mongorestore assumes admin.system.ver... Closed
is depended on by SERVER-25156 Create index version V2 Closed
is depended on by SERVER-25159 Default BSON validation version shoul... Closed
Documented
is documented by DOCS-9201 Not documented how to set featureComp... Closed
Related
is related to SERVER-25752 Adjust jstests to deal with setFeatur... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 18 (08/05/16), Query 2016-08-29
Participants:
Linked BF Score: 15

 Description   

setFeatureCompatibilityVersion(v) should do the following:
--Error if v is greater than the node's version or < 3.2.
On mongod (including config server):
--Set the version in admin.system.version to v.
On mongos:
--Send setFeatureCompatibilityVersion(v) to all shards and the config primary.

When a mongod (including config server) starts up:
--If admin.system.version contains a version higher than the node's version, fail.
--Run setFeatureCompatibilityVersion(3.4) on self if it is (1) started with no non-local databases, (2) a standalone or the primary of its replica set, (3) not run with --shardsvr.

addShard changes:
If the config server has admin.system.views, it sends setFeatureCompatibilityVersion(v) to the primary of the replica set being added, where v is the config server’s version in admin.system.version.

getAllParameters changes:
If admin.system.views is present, expose version in admin.system.version in getAllParameters.

Note: This command will no longer touch the admin.system.views collection, as the existence of this collection does not cause initial sync to fail on 3.2. Instead, we will use V2 indexes to cause 3.2 secondaries to fail. V2 indexes will be implemented in SERVER-25156.



 Comments   
Comment by Githook User [ 24/Aug/16 ]

Author:

{u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}

Message: SERVER-25155 featureCompatibilityVersion document should be created at replica set initiate time
Branch: master
https://github.com/mongodb/mongo/commit/831e20161e766b32b8ea0533077d231490e99883

Comment by Githook User [ 23/Aug/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-25475 SERVER-25155 Don't perform write for FeatureCompabilityVersion until replication is started up
Branch: master
https://github.com/mongodb/mongo/commit/dd74cff611986d34464fd4476e67dbcd6443d3ca

Comment by Githook User [ 19/Aug/16 ]

Author:

{u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}

Message: SERVER-25155 Create setFeatureCompatibilityVersion command
Branch: master
https://github.com/mongodb/mongo/commit/dc4a0797603401f7560199f15bd9dd29bd17b3a0

Comment by Tess Avitabile (Inactive) [ 19/Jul/16 ]

Need to consider what should happen if a local.config.repl document, but is not started as part of a replica set.

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