is it ok to start an mms agent on all mongo servers

[Grégoire Seux]

Hello,

I'd like to know if anybody has already started a mms agent on each
server of a cluster (45 nodes) and if there are issues arising.

mms doc states
>only one agent per group or environment will report to MMS at a time, but you can run multiple instances of the agent to provide redundancy.

but it is unclear if a lot of agent will cause trouble

maybe someone working in mms dev team?

The objective is to make all servers alike and thus minimizing custom
"role" in the cluster (all server have a mongoS for instance).

thanks

--
Grégoire

[Sam Millman]

I am not a mms dev or whatever however you shouldn't need to put mms on each replica/shard of a cluster. You should only need to put it on a server that can see the cluster through mongodb and it should just propogate the entire cluster to mms.

--
--
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com
To unsubscribe from this group, send email to
mongodb-user...@googlegroups.com
See also the IRC channel -- freenode.net#mongodb

---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Grégoire Seux]

On Tuesday, May 7, 2013 10:28:44 AM UTC+2, Sammaye wrote:

I am not a mms dev or whatever however you shouldn't need to put mms on each replica/shard of a cluster. You should only need to put it on a server that can see the cluster through mongodb and it should just propogate the entire cluster to mms.

Thanks for this answer.

I am aware I don't need to have one everywhere but it would drastically simplify the setup to have mms agent on each host.

I'd like an argumentative answer.

-- 

Grégoire

[Stephen Steneker]

On Monday, May 13, 2013 4:25:24 PM UTC+10, Grégoire Seux wrote:

I am aware I don't need to have one everywhere but it would drastically simplify the setup to have mms agent on each host.

Hi Grégoire,

You can certainly have multiple MMS agents, but only one will be actively reporting (the others act as hot standbys):

  http://mms.10gen.com/help/monitoring/deployment/#monitoring-architecture

I'm not aware of any limitations or caveats on multiple agents, but having 45 identical hosts seems excessive.

Within that group of hosts there must be some further roles such as replSet membership that would allow you to limit the number of agents running.  With that many hosts I would expect you are using an automated tool for deployment which would make this more manageable.

Regards,

Stephen

[Grégoire Seux]

Thanks for your answer.
Yes indeed, we use chef to manage our infrstructure and it allows to
specify specific conf for specific hosts. Having specific conf however
increases complexity that I wanted to avoid.
I have solved the issue by deploying mms agent on each mongoconf host
(or each member of replicaset for non sharded cluster).


--
Grégoire

[sam]

I don't believe having multiple MMS agents is fixing your issue.  Can you explain what you are trying to solve for?  You should only need one MMS agent to satisfy monitoring.

[Grégoire Seux]

On Mon, May 13, 2013 at 5:51 PM, sam <samnsa...@gmail.com> wrote:
> aving multiple MMS agents is fixing your issue. Can you explain what you
> are trying to solve for? You should only need one MMS agent to satisfy
> monitoring.

It allows to have some redundancy, in case one agent crash (for
instance because the host it runs crash) or is stopped for
maintenance.

--
Grégoire