[SERVER-49318] MongoDB repair failed due to Invariant failure rs.get() src/mongo/db/catalog/database.cpp Created: 05/Jul/20 Updated: 02/Aug/20 Resolved: 02/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, WiredTiger |
| Affects Version/s: | 3.4.24 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sirpa Vivek | Assignee: | Dmitry Agranat |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
MongoDB Version: 3.4.24 Repair Logs
Restart Logs
{{}} Is there a way to repair/recover the last part of the DB? or {{}} I would greatly appreciate the help. {{}} |
| Comments |
| Comment by Dmitry Agranat [ 02/Aug/20 ] |
|
We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Dmitry Agranat [ 26/Jul/20 ] |
|
We still need additional information to diagnose the problem. If this is still an issue for you, would you please upload:
Thanks, |
| Comment by Dmitry Agranat [ 16/Jul/20 ] |
|
As MongoDB 3.4 has reached EOL, we can try to recover the data as a one-time exception. As of today, the latest MongoDB version is 4.2.8. Is this node a part of the replica set? Please attach the following information:
Keep in mind that this repair effort may not be successful, and that diagnosing corruption issues requires significant information and effort. Thanks, |