[SERVER-25677] Config server can send wrong cluster ID to shards during addShard if cluster ID ever rolls back Created: 17/Aug/16  Updated: 25/Jan/17  Resolved: 26/Aug/16

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

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-08-29, Sharding 2016-09-19
Participants:

 Description   

The first time a config server becomes primary it builds the necessary indexes on the config database and initializes the config.version collection, which includes the cluster ID. It then immediately loads the cluster ID into memory. If the config.version document rolls back, however, we don't clear the cached in-memory cluster ID, so when a new config.version document is written, with a new cluster ID, we won't ever realize that its changed. This means that when we add a shard, we'll provide it the wrong clusterID in its shardIdentity document.



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

Author:

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

Message: SERVER-25677 Clear cached clusterId if config.version document is rolled back.
Branch: master
https://github.com/mongodb/mongo/commit/6bf9fd2e5a5f043b950cb77361be3c1ed7a7d0af

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