I meet a load distribution problem today and I browsed the Internet to find
out someone having the same problem but unfortunately, no one seems to
have. Here is my cluster configuration:
4 machines with 16 Go Ram (9600 Mo allocated to JVM)
8 core CPUs
Special cluster config: awareness of the vm host for shard primary and
replica allocation (to avoid having both a primary and a replica on the
same hardware).
I tried a (huge) insert today, and it leads to one of the 4 nodes having a
load average extremely higher than the three others (1.5 to 2 for the 3
"relax" servers vs. >12 for the high loaded one). I was thinking that
Elasticsearch was designed to avoid it. Am I wrong here?
I meet a load distribution problem today and I browsed the Internet to
find out someone having the same problem but unfortunately, no one seems to
have. Here is my cluster configuration:
4 machines with 16 Go Ram (9600 Mo allocated to JVM)
8 core CPUs
Special cluster config: awareness of the vm host for shard primary and
replica allocation (to avoid having both a primary and a replica on the
same hardware).
I tried a (huge) insert today, and it leads to one of the 4 nodes having a
load average extremely higher than the three others (1.5 to 2 for the 3
"relax" servers vs. >12 for the high loaded one). I was thinking that
Elasticsearch was designed to avoid it. Am I wrong here?
Thanks for your reply. I have the default 5 shards, but I have multiple
indexes, and all nodes have about the same number of shards on them.
Regards,
Loïc
Le mercredi 1 avril 2015 00:03:06 UTC+2, Jörg Prante a écrit :
Do you have your shards equally distributed over the 4 nodes? Or do you
use the default of 5 shards?
Jörg
On Tue, Mar 31, 2015 at 5:28 PM, Loïc Wenkin <loic....@gmail.com
<javascript:>> wrote:
Hi all,
I meet a load distribution problem today and I browsed the Internet to
find out someone having the same problem but unfortunately, no one seems to
have. Here is my cluster configuration:
4 machines with 16 Go Ram (9600 Mo allocated to JVM)
8 core CPUs
Special cluster config: awareness of the vm host for shard primary and
replica allocation (to avoid having both a primary and a replica on the
same hardware).
I tried a (huge) insert today, and it leads to one of the 4 nodes having
a load average extremely higher than the three others (1.5 to 2 for the 3
"relax" servers vs. >12 for the high loaded one). I was thinking that
Elasticsearch was designed to avoid it. Am I wrong here?
I meet a load distribution problem today and I browsed the Internet to
find out someone having the same problem but unfortunately, no one seems to
have. Here is my cluster configuration:
4 machines with 16 Go Ram (9600 Mo allocated to JVM)
8 core CPUs
Special cluster config: awareness of the vm host for shard primary and
replica allocation (to avoid having both a primary and a replica on the
same hardware).
I tried a (huge) insert today, and it leads to one of the 4 nodes having
a load average extremely higher than the three others (1.5 to 2 for the 3
"relax" servers vs. >12 for the high loaded one). I was thinking that
Elasticsearch was designed to avoid it. Am I wrong here?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
