I have a 3 nodes cluster with 5 active shards. Each node uses about 12GB of
The whole index contains approximately ~230 millions documents with two
The first type has something like ~100 millions of documents and there is a
parent-child relationship between those two types. I didn't implement any
custom routing, so I cannot make statements on how the documents are
allocated to shards.
As I was expecting, parent-child queries are slower than direct queries but
for the moment I cannot change this indexing schema. From my understanding,
it seems that each parent-child query is submitted to each shard from the
gateway and then results are sorted back.
So I was thinking: is it a good idea to reduce the number of nodes (to 2)
with a bigger amount of memory available each and also reducing the number
of shards (to 1 or 2 per node max)?
The main idea here is to reduce the network overhead when moving data
between shards and the gateway. Is it viable or am saying bullshits?
any hint will be appreciated,
thank you in advance,
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 firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.