for 2 days, I have a strange behavior with ElasticSearch. This is the
context:
1 clsuter with 3 node
os : debian
version 1.4.0 (official package)
OS mem : 12 Go
JMX : 8 Go
CPU : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
Nb CPU : 9
From 7 am Monday, I was an increase in the use of RAM. Recycling the
JMX is from once per day to once every 2 hours. I have no explanation.
The CPU is overused. The response time is 10 ms instead of 3,5mns.
Restarting each node has not changed anything.
Do you have a method or tools to diagnose ElasticSearch behavior ?
Should I upgrade to version 1.4.3 ?
I activated the index_search_slowlog.log. Is it possible to log the IP
of the machine in the slowlog ?
Thank you.
Alex.
On 17/02/15 15:17, Alexandre wrote:
Hello everyone,
for 2 days, I have a strange behavior with Elasticsearch. This is the
context:
1 clsuter with 3 node
os : debian
version 1.4.0 (official package)
OS mem : 12 Go
JMX : 8 Go
CPU : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
Nb CPU : 9
From 7 am Monday, I was an increase in the use of RAM. Recycling the
JMX is from once per day to once every 2 hours. I have no explanation.
The CPU is overused. The response time is 10 ms instead of 3,5mns.
Restarting each node has not changed anything.
Do you have a method or tools to diagnose Elasticsearch behavior ?
Should I upgrade to version 1.4.3 ?
for 2 days, I have a strange behavior with Elasticsearch. This is the
context:
1 clsuter with 3 node
os : debian
version 1.4.0 (official package)
OS mem : 12 Go
JMX : 8 Go
CPU : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
Nb CPU : 9
From 7 am Monday, I was an increase in the use of RAM. Recycling the JMX
is from once per day to once every 2 hours. I have no explanation. The CPU
is overused. The response time is 10 ms instead of 3,5mns. Restarting each
node has not changed anything.
Do you have a method or tools to diagnose Elasticsearch behavior ? Should
I upgrade to version 1.4.3 ?
Hello everyone,
for 2 days, I have a strange behavior with ElasticSearch. This is
the context:
- 1 clsuter with 3 node
- os : debian
- version 1.4.0 (official package)
- OS mem : 12 Go
- JMX : 8 Go
- CPU : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
- Nb CPU : 9
From 7 am Monday, I was an increase in the use of RAM. Recycling
the JMX is from once per day to once every 2 hours. I have no
explanation. The CPU is overused. The response time is 10 ms instead
of 3,5mns. Restarting each node has not changed anything.
Do you have a method or tools to diagnose ElasticSearch behavior ?
Should I upgrade to version 1.4.3 ?
Thank you.
Alex
--
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 elasticsearch+unsubscribe@__googlegroups.com
<mailto:elasticsearch%2Bunsubscribe@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/__msgid/elasticsearch/54E34D69.__6070800%40opendoc.net
<https://groups.google.com/d/msgid/elasticsearch/54E34D69.6070800%40opendoc.net>.
For more options, visit https://groups.google.com/d/__optout
<https://groups.google.com/d/optout>.
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.