[SERVER-53095] MongoDB 3.6.14 crashing on FreeBSD12.1 when unclean shutdown/reboot Created: 27/Nov/20 Updated: 27/Oct/23 Resolved: 13/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.6.14 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Akash Talole | Assignee: | Dmitry Agranat |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
FreeBSD12.1 UNIX |
||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
We have mongodb installed on Unix (FreeBSD12.1) VM. When hard reboot occurs due to vSphere HA or host issue, mongodb is crashing. When we are doing repair it gives attached error. It is found that WiredTiger.turtle file is empty after crash, which causing problem in repair. How to solve this issue?
Thanks and regards, Akash T |
| Comments |
| Comment by Dmitry Agranat [ 13/Jan/21 ] | |
|
We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | |
| Comment by Dmitry Agranat [ 29/Dec/20 ] | |
|
taloleakash@gmail.com, can you try using --repair with the latest MongoDB version, which is 4.4.3 after significantly increasing your node memory? In the backtrace I've noticed this:
| |
| Comment by Akash Talole [ 28/Dec/20 ] | |
|
MongoDB server version is 3.6.14. check mongo_recover_script.txt beforecrash_WiredTiger.turtle crashed_mongodb_logs.txt
| |
| Comment by Dmitry Agranat [ 28/Dec/20 ] | |
|
Thanks taloleakash@gmail.com, did you try to --repair it with the latest MongoDB version? The attached screenshot does not show what version was used and the --repair log lines & output. In my previous comment, I've requested:
But I could not find the wiredTiger.turtle after the crash. Please note that both files are needed after the crash but before your repair attempt. | |
| Comment by Akash Talole [ 23/Dec/20 ] | |
|
Hi Dmitry, This case is for standalone mongodb deployment. This is UFS filesystem. We are using local datastore of VMFS5 on vsphere. Check attached log files and mongodb files for before and after crash of mongodb. WiredTiger.turtle is empty after crash. aftercrash_sizeStorer.wt
| |
| Comment by Akash Talole [ 21/Dec/20 ] | |
|
Hi Dmitry, I will share additional information today. | |
| Comment by Dmitry Agranat [ 20/Dec/20 ] | |
|
We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the data mentioned in my last comment? Thanks, | |
| Comment by Dmitry Agranat [ 08/Dec/20 ] | |
|
The scenario you've described and the outcome should not have happened but we do not have enough information for the event. For example, you have not mentioned what filesystem is being used. MongoDB requires a filesystem that supports fsync() on directories. You can also try mongod --repair using the latest version of MongoDB. The ideal resolution is to perform a clean resync from an unaffected node. If the above fails, please provide:
Thanks, |