(You should really set Xms and Xmx to be the same.)
But it's not faulty, it's probably just GC which should be visible in the
logs. How much data do you have in your "cluster"?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 25 August 2014 21:19, Patrick Proniewski <elasticsea...@patpro.net>
wrote:
> Hello,
>
> I'm running an ELK install for few months now, and few weeks ago I've
> noticed a strange behavior: ES had some kind of stuck thread consuming
> 20-70% of a CPU core. It remained unnoticed for days. Then I've restarted
> ES, and it all came back to normal, until it started again 2 weeks later to
> consume CPU doing nothing. New restart, and 2 weeks later same problem.
>
> I'm running:
>
> ES 1.1.0 on FreeBSD 9.2-RELEASE amd64.
>
> /usr/local/openjdk7/bin/java -Des.pidfile=/var/run/elasticsearch.pid
> -Djava.net.preferIPv4Stack=true -server -Xms1g -Xmx2g -Xss256k
> -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
> -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
> -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch
> -Des.config=/usr/local/etc/elasticsearch/elasticsearch.yml -cp
> /usr/local/lib/elasticsearch/elasticsearch-1.1.0.jar:/usr/local/lib/elasticsearch/*:/usr/local/lib/elasticsearch/sigar/*
> org.elasticsearch.bootstrap.Elasticsearch
>
> # java -version
> openjdk version "1.7.0_51"
> OpenJDK Runtime Environment (build 1.7.0_51-b13)
> OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
>
> Here is a sample top output showing the faulty thread:
>
> last pid: 37009; load averages: 0.79, 0.73, 0.71 up
> 53+18:11:28 11:48:59
> 932 processes: 9 running, 901 sleeping, 22 waiting
> CPU: 10.8% user, 0.0% nice, 0.2% system, 0.0% interrupt, 89.0% idle
> Mem: 4139M Active, 1129M Inact, 8962M Wired, 1596M Free
> ARC: 5116M Total, 2135M MFU, 2227M MRU, 12M Anon, 133M Header, 609M Other
> Swap: 4096M Total, 4096M Free
>
> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND
> ../..
> 74417 elasticsearch 33 0 2791M 2058M uwait 5 153:33 23.97%
> java{java} <--
> 74417 elasticsearch 27 0 2791M 2058M uwait 7 43:02 7.96%
> java{java}
> 74417 elasticsearch 27 0 2791M 2058M uwait 6 43:02 7.96%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 1 7:32 2.20%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 5 8:26 1.76%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 7 8:25 1.76%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 5 8:25 1.76%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 5 8:26 1.66%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 7 8:26 1.66%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 4 8:25 1.66%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 6 8:25 1.66%
> java{java}
> 74417 elasticsearch 22 0 2791M 2058M uwait 1 8:25 1.66%
> java{java}
>
> Nothing to be found in log files...
>
> Any idea?
>
> Patrick
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/7C4F5EC0-BA5D-4D8C-AB39-EEA4250956DC%40patpro.net
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAEM624Z2AiKZPs2EoQDSqAvYLVzAwJvwC%3DiFV4G4f6OGPcPOCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
