[SERVER-26036] Error when recovering failed replicaset Created: 09/Sep/16 Updated: 27/Oct/16 Resolved: 27/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 3.2.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Vincent van Megen | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Upgraded last member of replicaset (3 members) from 3.2.8 to 3.2.9. |
| Participants: |
| Description |
|
| Comments |
| Comment by Kelsey Schubert [ 27/Oct/16 ] | |
|
Hi vincentvm, I've taken another look at the stack trace you have provided, and believe that the following message was likely logged immediately preceding the backtrace:
This error indicates that the underlying storage layer is at fault, and I would recommend ensuring the integrity of your storage layer. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, | |
| Comment by Vincent van Megen [ 11/Oct/16 ] | |
|
Unfortunately I don't have the diagnostic data anymore. | |
| Comment by Kelsey Schubert [ 04/Oct/16 ] | |
|
Hi vincentvm, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the complete logs of the affected node? Thank you, | |
| Comment by Kelsey Schubert [ 12/Sep/16 ] | |
|
Hi vincentvm, Thank you for opening for opening this ticket and providing the backtrace. So we can continue to investigate this issue, would you please upload the following information?
I've created a secure upload portal for you to use here. Files uploaded to this portal are only visible to MongoDB employees investigating this issue and are routinely deleted after some time. Thanks again, |