Re: How to get mappings using the Java API with ElasticSearch 0.90.10 and 1.0.0 RC1

2014-01-28 Thread Roy Russo
Just a side note that the API response format changed in 1.0.0RC1. http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/_indices_apis.html On Tuesday, January 28, 2014 3:15:57 AM UTC-5, Thierry Templier wrote: Hello, I wonder what is the best way to get the mappings for an

Re: For those wanting to try Marvel

2014-01-28 Thread Roy Russo
Although I agree with the code transparency in principle, it isn't a sound business idea. Scaling an OSS company on support/services revenue alone is very linear and that's not something investors want. You also risk becoming a consulting company, rather than a software distributor. In the

Re: A Question on Plugin redundancy

2014-01-22 Thread Roy Russo
Lukas, Yes, very similar approach in tech, but different in distribution model. The use of RRD makes sense for them, as I believe their offering monitors more than just ES clusters. It's a New Relic type of model. Alternatively, New Relic has ES monitoring plugins available as well. On

Re: A Question on Plugin redundancy

2014-01-21 Thread Roy Russo
with installing plugins in all nodes? -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 21 janv. 2014 à 19:57, Roy Russo royr...@gmail.com javascript: a écrit : Hello all, Curious here on what is the recommended way of plugin deployment in a cluster, for redundancy

Re: A Question on Plugin redundancy

2014-01-21 Thread Roy Russo
Hi Lukas, Somewhat... The idea is a monitoring 'service'. Hosted. Where its hosted is a separate conversation. I agree with most everything you stated. Having a local agent running is the way to go. I'm avoiding remote polling and little to no advantage in distributing as a plugin. The one

1.0.0RC1 breaking changes : GC stats

2014-01-20 Thread Roy Russo
Well, not sure if it qualifies as a breaking change, unless you cowboy code javascript like I do ;-) The node stats api (/_nodes/{this.nodeId}/stats?all=1) is returning a different format for JVM GC now, splitting old and young generations (which is really helpful) I didn't notice this change

[ANN] ElasticHQ v1.0.0 (ElasticSearch v1.0.0.RC1 Support)

2014-01-20 Thread Roy Russo
are displayed on the Diagnostics Screen *Every HQ release is always backwards compatible*, so there's no magic needed on your part. As always, you can get it here: http://www.elastichq.org/gettingstarted.html Regards, Roy Russo http://www.elastichq.org/blog/ -- You received this message

1.0.0RC1 broken changes

2014-01-15 Thread Roy Russo
Hello, So it appears a few APIs have changed in 1.0.0RC1 (which is bizarre considering I tested on master just last week and everything worked, but whatever...) Any ideas when the documentation will be updated to reflect the changes? I'm having a hard time mapping old API calls to the new

Re: 1.0.0RC1 broken changes

2014-01-15 Thread Roy Russo
the master docs http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/index.html Looks like your call should be: /_nodes/4oL7COyQTNiQPa4xZ76Pfg/stats?all=trueplugin=true Thanks, Matt Weber On Wed, Jan 15, 2014 at 12:31 PM, Roy Russo royr...@gmail.comjavascript: wrote