You could test with a single index and get an idea of write performance on
single one. One nice thing about ES is it scales almost linear, more
concurrent indices setup for writing, better write performance.
--
You received this message because you are subscribed to the Google Groups
It's good to hear more demands on security, as that's one big concern for
commercial usage.
If you are fine with the model of open to only given group of people,
you could try plugin( jetty ) and try enable authentication from there(not
something out of box). But that is just some workaround. You
How many NIC are there on each of your nodes? We got some issue on boxes
with 4 NIC, some address were not reachable due to linux kernel setting.
I'd suggest you test the full connection matrix via some shell script, so
as to rule out this cause.
My 2 cents
--
You received this message because
We have a cluster with 10 nodes, 48g heap for each ES process. The total
indexing rate is about 25000 doc per second, about 20 indices actively
receiving new data. I'm really courious to compare and evaluate the
indexing performance numers.
Thanks!
--
You received this message because you are
I have found quite a few simliar emails about capacity planning. Although
it make sense that there are a lot of variables/factors, it would be great
for new users to have some sort of baseline, which could be simple , just
single type of indices, not too heavy load. Maybe there are already
Hi Robert,
For the comment of 32g heap, I do notice the same recommendation in
official guide. But it don’t seems to make senses to give only 25% ram to
ES as there is total 128g. One alternative could be 2 ES processes per
node, but it would be a bit difficult to manage. Does anyone have
Hi Robert,
Thanks for the detailed info. Here is what we have: 10 data only nodes,
192g ram each, 64g given to ES, java6. We have more than 40 indices
actively receiving new data. Max indexing rate for a single index is 3k/s,
total rate us around 50k. We still found timeout occasionally, but it
The most surprising part of my upgrade from 0.90 to 1.0.1 was the drop of
indexing performance. So, yes, I’m also interested to know any gotchas.
2014年11月20日 下午8:47于 Jason Wee peich...@gmail.com写道：
I would be interested too, we are using the same 0.90.7 version.
Jason
On Thu, Nov 20, 2014 at
Hi,
I was using marvel in my test environment. As we had authentication
plugin on the REST interface, and noticed the error like:
marvel.agent.exporter ... failed to upload index template, stopping export
I’m pretty sure it’s blocked by the auth plugin, but the question is why
would marvel
Hi Boaz,
Yes REST interface got less compatibility issue. The only downside for us
is lacking proper authentication header in its REST request. Is there any
plan to support both REST and tranport interface?
Another question, what ’s the version range supported by existing marvel?
If I
Sorry you answered the ersion range question already:)
Thanks!
--
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 elasticsearch+unsubscr...@googlegroups.com.
To
The value “200” to me is http response code. You can find other value if
your node can’t join the cluster, 503 in such case.
Cheers!
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from
12 matches
Mail list logo
