[SERVER-8596] Upgrade process from 2.2 to 2.4 does not clean up "upgradeId" and "upgradeState" fields in config.version Created: 15/Feb/13  Updated: 11/Jul/16  Resolved: 20/Feb/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.0-rc0
Fix Version/s: 2.4.0-rc1

Type: Bug Priority: Major - P3
Reporter: Michael O'Brien Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

To reproduce:

  • Run a sharded cluster on 2.2 that contains at least one collection created in 2.0.
  • Start up a mongos with the --upgrade flag to start the process of converting chunks metadata to have the "lastModEpoch" field
  • After mongos is up and running:

    { "_id": 1, "version": 3, "minCompatibleVersion": 3, "currentVersion": 4, "clusterId": ObjectId("511eb84c6e9141cef5f7a0ab"), "upgradeId": ObjectId("000000000000000000000000"), "upgradeState": { } } 

The upgradeId and upgradeState fields are still there.



 Comments   
Comment by auto [ 20/Feb/13 ]

Author:

{u'date': u'2013-02-20T20:22:35Z', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: SERVER-8596 cleanup upgradeId field after upgrade
Branch: master
https://github.com/mongodb/mongo/commit/01c2aa306374e440dc24f47c529ea075618aa20c

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