[SERVER-9661] config upgrade fails if collection missing "key" field Created: 13/May/13  Updated: 11/Jul/16  Resolved: 13/May/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.3
Fix Version/s: 2.4.4, 2.5.0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
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
Participants:

 Description   

Seems like, at least in some cases, config upgrade will fail if the "key" field is missing in a config.collections entry. This can happen on a collection drop.



 Comments   
Comment by auto [ 22/May/13 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-9661 config upgrade v0->v3 fails when dropped collection has noBalance set
Branch: v2.4
https://github.com/mongodb/mongo/commit/c34d5a987b25ec72b989077769435404ad7d3608

Comment by auto [ 13/May/13 ]

Author:

{u'date': u'2013-05-13T16:30:49Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-9661 config upgrade v0->v3 fails when dropped collection has noBalance set
Branch: master
https://github.com/mongodb/mongo/commit/a13b441926ada81d805172aa94243164858c012f

Comment by Greg Studer [ 13/May/13 ]

In 2.4.3, only happens if unique or noBalance was set on the dropped collection.

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