When I'm starting or restarting ES service, its CPU use hovers at 3% CPU
which is great. After some time and some use the CPU use will climb to
30%-100% and stay about that level even when idle. The first time it
happens flushing helps - after the flush CPU level returns to the nice and
pleasant 3% but eventually even that stops helping and only the service
restart does the trick.
30%-100% CPU use could be tolerated theoretically since the server has
multiple CPUs, but it's a VPS and I don't want to use more resources than I
need. ES works perfectly with 3% CPU use before it starts misbehaving.
What I want to figure most of all is why that happens and ideally make it
stay at the 3% level all the time, but I'm not sure how to go about
Hot threads: https://gist.github.com/kaitnieks/9363338
1 node, 300 indices
happens with and without network.tcp.blocking, but when
network.tcp.blocking is false, CPU use seems to be a little higher.
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0566e0b0-16cc-4f16-a297-2e187b0cbdcc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.