[DOCS-2962] Change advice on running agent Created: 21/Mar/14 Updated: 16/Mar/15 Resolved: 04/Apr/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Page | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 45 weeks, 6 days ago | ||||
| Description |
|
http://mms.mongodb.com/help/monitoring/faq/#where-should-i-run-the-monitoring-agent Isn't true. Running the agent on a mongoD box is always a bad idea. I've had people run into trouble doing it on a three node replica set. Then there were the guys who brought there mongoD box for maintenance in the middle of Black Friday with the MMS agent on it.... 2 agents per MMS group(one as a hot backup) not on mongoD boxes in the advice we should give. Add in some whys too. Operational (i.e. you shut the host down) and load (the mongoD gets overloaded and everything on the box stops) |
| Comments |
| Comment by Githook User [ 03/Apr/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |