[SERVER-57379] "WiredTiger error when building index. Created: 03/Jun/21 Updated: 17/Jun/21 Resolved: 15/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jongsun moon | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | build, index | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
| Comments |
| Comment by jongsun moon [ 17/Jun/21 ] |
|
Hi Edwin Zhou,
Thank you very much for your help.
Regards,
|
| Comment by Edwin Zhou [ 15/Jun/21 ] |
|
Unfortunately we aren't able to repair this level of corruption. To avoid a problem like this in the future, it is our strong recommendation to:
Best, |
| Comment by jongsun moon [ 15/Jun/21 ] |
|
Hi Edwin Zhou, We have only one mongod server which is set as replica set 0(One mongos + one config server + one mongod server). So we can not do a clean resync. Is there any other thing to do for it?
|
| Comment by Edwin Zhou [ 11/Jun/21 ] |
|
Given that your topology appears to be a replica set, we may be able to resolve this corruption by doing a clean resync from an unaffected node. We look forward to hearing if you're able to find success with this method. Best, |
| Comment by jongsun moon [ 11/Jun/21 ] |
|
Hi Edwin Zhou, Unfortunately, --repair operation was failed.
Regards, |
| Comment by Edwin Zhou [ 09/Jun/21 ] |
|
Thank you for providing the output of the db.collection.validate command. It indeed confirms that there is collection level corruption. We look forward to hearing back to you with the results of running --repair. In the event that a --repair operation is unsuccessful, then please also provide:
Best, |
| Comment by jongsun moon [ 08/Jun/21 ] |
|
other collections validation result
At the same database, I made same collection and built index (previous collection was renamed) and I received below.
And then I ran collection validation and found corrupted records.
Now I am doing "mongod --repair".
|
| Comment by jongsun moon [ 08/Jun/21 ] |
|
Hi Edwin Zhou. Thank you for your reply. I ran db.collection.validate. Then I got message below. (I attached log file at the bottom.) And file size ("collection-20-7619064565122544008.wt" which faced error in log) is 482GB. Is there anything to do for it? Regards,
Regards,
|
| Comment by Edwin Zhou [ 07/Jun/21 ] |
|
It appears there may be some corruption on the collection level. I advise you to first make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. Then, can you run db.collection.validate on the affected collection? Best, |