-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MongoDB server crashes several times a week #144
Comments
Notes from reading mongodb log: Some context
and
Errors
and
|
Applied mongodb's "warning" recommendations (Disable Transparent Huge Pages (THP)). After rebooting the droplet, the warning disappears from mongodb's logs! 👌 |
About having mongodb to use only SDD instead of RAM:
|
Solutions to reduce mongob RAM usage (if still necessary): Reduce size of WiredTiger internal cache
=> 60% * 3 - 1 = 1.8 -1 = 0.8 GB on our current (3gb-ram) instance It's possible to manually set this using the Limit mongod process usage using cgroups |
The server has not crashed for 2 weeks! 🎉 |
It crashed again on February 22nd, 2020, while I was in vacation in Scotland => I activated a process monitor on Datadog |
Just letting you know, you're not alone. I have my scripts just auto-restart mongo at this point; it randomly crashes after running for long periods of time! I can only assume it's due to the small amount of memory available to it, but that's not an acceptable reason. |
Thanks for sharing your experience, Coty, it really makes me feel better to see that we're not alone to experience this! The fact that you also run it on a machine with a tight amount of memory kinds of confirm that lack of memory could be the root cause of this problem. Thank you and have a great week! |
Makes sense: Related: #202 |
Contributes to #318, #202 and #144. cf #318 (comment) * remove /styles pages * remove /genre routes
## [1.37.7](v1.37.6...v1.37.7) (2020-11-10) ### Bug Fixes * Remove slow routes ([#386](#386)) ([0ac5e41](0ac5e41)), closes [#318](#318) [#202](#202) [#144](#144) [/github.com//issues/318#issuecomment-724748867](https://github.com//github.com/openwhyd/openwhyd/issues/318/issues/issuecomment-724748867)
Are these scripts written inside node ( I mean can I restart mongo service when I know it has crashed ) ? |
I know it does not answer your question, but it may help you to know that my MongoDB instance has been running without interruptions since I made sure to close cursors after opening them, see https://github.com/openwhyd/openwhyd/pull/405/files#diff-5ad5ab59edde086d4dc1e2ad75d0637631903bb6ae760e7581ee7ea1dc0ed961R147. |
Crashes were much more frequent when mongodb+nodejs were running on a 2gb-ram instance, than now on a 3gb-ram instance. But still, I need to manually run
sudo service mongodb restart
several times a week, whenever openwhyd users see a "502 Bad Gateway" page while trying to access openwhyd.org. (e.g. https://www.facebook.com/groups/openwhyd/permalink/2056648404616708/)Hypothesis:
Next steps:
/var/log/mongodb/mongod.log
The text was updated successfully, but these errors were encountered: