Thank you for answers Jörg. I really appreciated your helps :-).
On Thursday, September 25, 2014 7:07:51 PM UTC+3, Jörg Prante wrote:
>
> What you see are some of the TCP/IP stack counters of your hardware
> network interface since it was started. It is provided by the OS and read
> by sigar
>
What you see are some of the TCP/IP stack counters of your hardware network
interface since it was started. It is provided by the OS and read by sigar
http://www.hyperic.com/support/docs/sigar/org/hyperic/sigar/Tcp.html
It is not related to ES or to ES specific connections. It's just a
nice-to-hav
Thank you for your answer Jörg. I remove them in conf file but my
performance problem continues. I have another question about it. My
network stat is that;
curl -XGET 'http://localhost:9200/_nodes/stats/network?human&pretty'
{
"cluster_name" : "test-cluster",
"nodes" : {
"XB95yJZhS7WLAP
Do not manipulate the threadpool to "fixed" and do not use such high
numbers like 100,600, 5000, 5 This will sooner or later congest
your machine. The long list of threads in OS is just one (harmless) symptom
of a misconfiguration. Use the default setting.
Do not use 80% buffer for index.
Can you post your settings from config/elasticsearch.yml?
Jörg
On Thu, Sep 25, 2014 at 9:03 AM, Umut Yerci wrote:
> Elasticsearch runs on my low-configured system which has 4G memory and 4
> cores CPUs. I get high-cpu usage problem with ES. Even after closing
> analyzer(s), reduce threads size
