One out of 4 nodes always spikes to 100% CPU when we do some load tests using JMeter (50 Threads, 50 Loops) with any query (Match_All, Filtered Query etc.,). That particular node has 3 Shards with 2 Primary Shards. The other nodes have less than 40% CPU on them at the same time. The heap is set at 30GB on all of them. This is the GIST for Hot Threads <https://gist.github.com/RobloxSai/9f040bbd5ab7b58f2b1d> when the Test was running. Is there anything else that can be done to improve the performance? The Query Response times jump to 5-8 seconds when the CPU is hammered.
<https://lh3.googleusercontent.com/-EDnXAEg34cA/U6I5fb2zNOI/AAAAAAAAAB4/DqybJhq3Yhc/s1600/4+Nodes+Setup.png> I had previously posted the specs of the Servers on another thread <https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/elasticsearch/P1o_4bVvECA>. Here are the Server Specs: *Machine Specs:* Processor: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz Number of CPU cores: 24 Number of Physical CPUs: 2 Installed RAM: [~256 GB Total] 128 GB 128 GB 16 MB Drive: Two 278GB SAS Drive configured in RAID 0 *OS:* Arch: 64bit(x86_64) OS Type: Linux Kernel: 2.6.32-431.5.1.el6.x86_64 OS Version: Red Hat Enterprise Linux Server release 6.5 (Santiago) Java Version: Java 1.7.0_51 (Java 7u51 x64 version for Linux). -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4c80c557-c85d-4319-b7cc-ddd2aebdbd95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
