[SERVER-30099] Error with wiredTiger.wt Created: 12/Jul/17 Updated: 14/Aug/18 Resolved: 19/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kesava Raju Mudunuri [X] | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | docker, envc, envm, rge, rpu, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Steps To Reproduce: | it terminal i run mongod |
| Participants: |
| Description |
|
| Comments |
| Comment by Mark Agarunov [ 19/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello KesavMR, Thank you for the response. Unfortunately the error you are seeing indicates that there is underlying corruption of the database which cannot be repaired. My recommendation would be a clean resync from a node that is not affected if possible or restoring from a backup. To prevent this type of problem in the future, we recommend implementing regular backups and/or replication to mitigate any issues related to unreliable storage layers or server failures. Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kesava Raju Mudunuri [X] [ 12/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Mark Agarunov, Complete story is like this #Original file are in AWS EC2 instance
If you need any further information let me know. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kesava Raju Mudunuri [X] [ 12/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Mark Agarunov, I am not able to connect after extracting files you provided. Following the complete log of it.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 12/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello KesavMR, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you please extract these files and replace them in your $dbpath and let us know if it resolves the issue? If you are still seeing errors after replacing these files, please provide the complete logs from mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:
Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kesava Raju Mudunuri [X] [ 12/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Mark Agarunov, Thank you for response. I have uploaded the files. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 12/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello KesavMR, Thank you for the report. To further troubleshoot this issue, I would like to request a couple of files. Please upload the following:
With these files, we can attempt a repair, although please note that there is no guarantee that the repair will be successful. Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kesava Raju Mudunuri [X] [ 12/Jul/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
As mongo size reached 90 gb. We are getting timeout errors for non index fields. So, i try to index those fields. When i am on it, mongo got corrupted and not able run anymore. So, try to repair it. But, later it stopped working.Then it showing error in WiredTiger.wt file. |