[SERVER-8316] Config upgrade v3 to v4 fails when old upgrade collections doesn't exist on the server Created: 24/Jan/13  Updated: 11/Jul/16  Resolved: 24/Jan/13

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

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

Operating System: ALL
Participants:

 Description   

If a previous upgrade failed, it's possible that the previous upgrade collections are missing. We try to clean these up as part of the upgrade process, but failing to clean the collections up shouldn't abort the upgrade.



 Comments   
Comment by auto [ 24/Jan/13 ]

Author:

{u'date': u'2013-01-24T15:48:42Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}

Message: SERVER-8316 minor cleanup of ping document warnings
Branch: master
https://github.com/mongodb/mongo/commit/358794215a51f3dc8b646ad22eaad6f5e4444c5d

Comment by auto [ 24/Jan/13 ]

Author:

{u'date': u'2013-01-24T15:27:06Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}

Message: SERVER-8316 make config upgrade more tolerant of missing collections from last upgrade
Branch: master
https://github.com/mongodb/mongo/commit/962f53dc4e3245fa3979cdc24cf1d8d339e0bc0d

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