I have just created a issue:
https://github.com/elasticsearch/elasticsearch/issues/6463
Regards.
Em quinta-feira, 5 de junho de 2014 20h02min05s UTC-3, Mark Walkom escreveu:
This would probably be worth raising as a github issue -
https://github.com/elasticsearch/
Regards,
Mark Walkom
On Thursday, 5 June 2014 00:54:15 UTC+2, Jörg Prante wrote:
Why do you use terms on _id field and not the the ids filter? ids filter
is more efficient since it reuses the _uid field which is cached by default.
So does the terms filter. The only advantage of the _ids filter is that
you
Hi Jörg. Thanks for your reply again.
As I said, I already had used ids filter, but I got the same behaviour.
I realized what was wrong. Maybe it could be a bug in ES or not. When I
executed the filter I included from and size attibutes. In this case
size was 99, but the final result
This would probably be worth raising as a github issue -
https://github.com/elasticsearch/
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 5 June 2014 22:38, Marcelo Paes Rech marcelopaesr...@gmail.com wrote:
Hi
Hi Jörg. Thanks for your reply.
Here is my filter.
{filter:
{
terms : {
_id : [ QSxrbEM8TKe5zr8931xBjA, wj63ghegRwC6qLsWq2chkA,
hYEhDbAqQwSRxhYfvDgFkg, 4bZmPE1fTYqijphRyyWiuQ,
Fhq53yYyT3CEw6vclKu_NA, XL2atBraTEyx57MefjFVhA,
951i0dZkT064FlQkzHnnWA, O8Ixbir1TrGT_IA3wKfsHg,
Why do you use terms on _id field and not the the ids filter? ids filter is
more efficient since it reuses the _uid field which is cached by default.
Do the terms in the query vary from query to query? If so, caching might
kill your heap.
Another possible issue is that your query is not
Thanks for your reply Nikolas. It helps a lot.
And about the quantity of documents of each shard, or size of each shard.
And the need of no data nodes or only master nodes. When is it necessary?
Some tests I did, when I increased request's number (like 100 users at same
moment, and redo it
Can you show your test code?
You seem to look at the wrong settings - by adjusting node number, shard
number, replica number alone, you can not find out the maximum node
performance. E.g. concurrency settings, index optimizations, query
optimizations, thread pooling, and most of all, fast disk
Hi guys,
I'm looking for an article or a guide for the best cluster configuration. I
read a lot of articles like change this configuration and you must
create X shards per node but I didn't saw nothing like ElasticSearch
Official guide for creating a cluster.
What I would like to know are
