Handling Bus Error in Mongo Service I have a Mongo service with which multiple hosts are interacting. The host on which the Mongo service is running is quite special -- it has 3TB of RAM. However, that host also throws intermittent Bus Error responses. If a Bus Error occurs within the Mongo service process, the service is halted and all celery (Python) processes that are interacting with the resource are served Connection Refused responses.

Is there a way to allow the Mongo service to somehow recover from a Bus Error? Can sharding help with this problem? Is there some other potential solution to the Bus Error that can be made at the application configuration level? I'd be grateful for any suggestions others can offer on this question!

I built Mongo from source on RedHat so I can use any recent version if that helps. The currently installed version is 3.6.4.
Handling Bus Error in Mongo Service


As per MongoDB documentation here It would also be helpful to run smartctl (part of smartmontools) to check for SMART hardware errors:

sudo  smartctl -a /dev/sdb


Even you can run the Linux fsck utility is used to check and repair Linux filesystems (ext2, ext3, ext4, etc.).

Depending on when was the last time a file system was checked, the system runs the fsck during boot time to check whether the filesystem is in consistent state. System administrator could also run it manually when there is a problem with the filesystems.

Make sure to execute the fsck on an unmounted file systems to avoid any data corruption issues.

For your further ref here and here