[SERVER-8304] config upgrade v3 to v4 too paranoid about config.collection formats Created: 23/Jan/13  Updated: 11/Jul/16  Resolved: 25/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   

.. it's possible to get documents of the type:

{ _id : collName, lastmod : new Date(...), dropped : true }

...which are rejected by our parser as invalid before the upgrade can happen. We should modify the parser or the upgrade process to handle this case gracefully (by ignoring the collection).

Workaround is to manually remove the dropped collection entry.



 Comments   
Comment by auto [ 25/Jan/13 ]

Author:

{u'date': u'2013-01-23T20:51:26Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}

Message: SERVER-8304 dropped collections shouldn't have sharding info
Branch: master
https://github.com/mongodb/mongo/commit/a0a114ba8baf09ed45d9ea8f1307fc604d12c1e7

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