[SERVER-15156] MongoDB upgrade 2.4 to 2.6 check returns error in config.changelog collection Created: 05/Sep/14 Updated: 11/Mar/15 Resolved: 09/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | 2.6.5, 2.7.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Buchanan | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Completed: | |||||
| Steps To Reproduce: | Run db.upgradeCheckAllDBs() on mongo 2.6 shell, connected to a 2.4 mongos instance. |
||||
| Participants: | |||||
| Description |
|
In running the db.upgradeCheckAllDBs() command to check for issues in order to upgrade from MongoDB 2.4 to 2.6, an error is reported:
I don't think the _id index check should occur on collections in the config database, right? This check is skipped for several other internal collections. Is it safe to ignore this error and move forward with the upgrade if no other errors are reported? |
| Comments |
| Comment by Githook User [ 10/Sep/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: (cherry picked from commit 4da87914c4ad2b3ca34cd0008a57faa2c068db85) |
| Comment by Githook User [ 09/Sep/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Jason Buchanan [ 07/Sep/14 ] |
|
Dan, Yes, this shared cluster was created with mongodb version 2.0, maybe even 1.8. Will ignore the error and proceed. Thanks! |
| Comment by Daniel Pasette (Inactive) [ 06/Sep/14 ] |
|
Jason, |