5 ms·
The solution is simple; use a tool to keep an eye on MongoDB, make a best guess of your capacity (flush time, queue lengths, lock percentages and faults are goo
by rgarcia 14y ago
The solution is simple; use a tool to keep an eye on MongoDB, make a best guess of your capacity (flush time, queue lengths, lock percentages and faults are good gauges) and shard before you get to 80% of your estimated capacity.
Any recommendations for such a tool?
- ukd1 14y agoMMS (https://mms.10gen.com/user/login https://mms.10gen.com/user/login) from 10gen is pretty good - it's very mongo specific. I've also used Munin (http://munin-monitoring.org/ http://munin-monitoring.org/, there is a great plugin - https://github.com/erh/mongo-munin https://github.com/erh/mongo-munin), CloudWatch (http://aws.amazon.com/cloudwatch/ http://aws.amazon.com/cloudwatch/) and various in-house ones as well.
- alexmic 14y agoI've been using MMS for about a year now, and I've found their agent to be not-so-great. I keep getting random alerts about the agent being down and then up again. Other than that, it's descent and free!
- gianpaj 14y agoHow would you use CloudWatch to monitor MongoDB? Or do you mean that you can get statistics from the Amazon EC2 mongo instance(s) with Munin and a cloudwatch plugin?
- ashayh 14y agoThe Zabbix mongodb plugin also looks like a good option: http://code.google.com/p/mikoomi/source/browse/#svn%2Fplugins%2FMongoDB%20Plugin http://code.google.com/p/mikoomi/source/browse/#svn%2Fplugin...