[SERVER-26901] Invariant failure on startup when upgrading from 3.0.3 Created: 03/Nov/16 Updated: 04/Nov/16 Resolved: 04/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 3.0.13 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Sumeet Patel | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian (Jessie) |
||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Upgrade from 3.0.3 to 3.0.13 on Debian Jessie which has been upgraded from Squeeze (Mongo 2.2.6) The blocking error on startup was: I guess the error reason could have been more informative at the least. Jumping over 3.0.13 to 3.2.10 didn't resolve the issue. My practical solution was to purge the data files and then re-sync up to my primary running 3.0.3, moving from mmapv1 to wiredtiger as the storage engine, then swap roles and upgrading and so forth. Apologies for the missing top of the log.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: |
| Description |
|
I was upgrading an environment, Debian (Squeeze) running Mongodb 2.2.6. |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Nov/16 ] | |
|
The error message:
is indicative of data corruption in this node, most typically caused by unreliable storage. The right solution is to resync from a healthy node, as you already did. I'm therefore closing this ticket. In the future, please post on the mongodb-user group or Stack Overflow with the mongodb tag for MongoDB-related support requests, where your question will reach a larger audience. Thanks, |