At seemingly random intervals, the ElasticSearch Java process starts
hogging all CPU on my machine. This is in a two-node cluster where one node
is gathering data from other sources and continuously updating the
documents. Documents time out when they haven't been updated for a while.
The documents get replicated to the other node in a single shard setup.
This happened without any querying going on aside from very trivial health
The node actually performing the updating starts using max CPU until I
restart ElasticSearch, but I can't figure out why. To show the effect,
here's a Ganglia graph:
This is a 24GB machine with 24 cores, running ElasticSearch 1.0.1 on
OpenJDK 7. I took a long snapshot of hot_threads when it was happening,
it's available over here:
I was wondering whether someone had seen this before or had any clue why
this is happening.
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e7ecc7db-b310-448f-8d09-c3985e6c3564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.