Hi Jorg, I think gatherer may be a little heavy for what I'm trying to achieve. What I'm working on can be compared to MMS: https://mms.mongodb.com/learn-more#monitoring
Simple idea. No magic. I like to delude myself in to thinking its the next phase for ElasticHQ. ;-) Lukas has a point in that distribution as a plugin is not ideal, as a monitoring agent should not be affected by the system it is monitoring - not intimately tied. Lukas, Didn't know of RHQ. I was there for JBossON. On Tuesday, January 21, 2014 1:57:18 PM UTC-5, Roy Russo wrote: > > Hello all, > > Curious here on what is the recommended way of plugin deployment in a > cluster, for redundancy on that plugin. Say I have 10 nodes... I deploy a > plugin on Node1. Node1 dies. Now what? I may have a new master node, but my > plugin is gone. > > Is there an idea of deploying plugins on every node, and having only the > elected master be the "active" plugin? > > Excuse me if it's a dumb question. I can't seem to find the answer > anywhere. > > Regards, > Roy Russo > http://www.elastichq.org/ > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f69b698e-47cd-48d6-b738-76f7a059a5e3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
