How many shards to use is a complicated question and depends on the
specific use case. For testing in this scenario though, it's likely that
just matching the number of nodes you have would be a good choice. Then you
will have 1 primary shard for each index on each node.
That said it also looks li
Here is the .yml part for the shards
# Set the number of shards (splits) of an index (5 by default):
#
index.number_of_shards: 64
# Set the number of replicas (additional copies) of an index (1 by default):
#
index.number_of_replicas: 1
I have it set to 64 shards and 1 replica. Is there a rec
That's a massive number of shards! As Kimbro pointed out, that's likely
your problem.
On 23 January 2015 at 06:04, Kimbro Staken wrote:
> Yes you have something very wrong. That is showing you have a huge number
> of shards and the cluster is obviously struggling to allocate all of them.
> You s
Yes you have something very wrong. That is showing you have a huge number
of shards and the cluster is obviously struggling to allocate all of them.
You said you have 9 nodes and 1 replica but you didn't specify how many
shards per index?
Kimbro
On Thu, Jan 22, 2015 at 11:45 AM, Sam Flint wrote:
Hi,
I am evaluating elastic search for a data warehouse project. I have a
9 node cluster with 1 replica. I have loaded 6 days worth of data.
Things seem sluggish all around. Here is the health of the nodes
{
"active_primary_shards": 9251,
"active_shards": 13509,
"cluster_
