Apologies, the gist link wasn't working properly: https://gist.github.com/Kaidence/2b95c207f4e6a79841c5<https://gist.github.com/Kaidence/2b95c207f4e6a79841c5>
On Thursday, March 27, 2014 1:00:35 PM UTC-7, Jos Kraaijeveld wrote: > > 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 > checks. > > 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: > > > <https://lh4.googleusercontent.com/-P_81cbz2uQU/UzSCGjuJzNI/AAAAAAAAAB8/2zSevfkpN3c/s1600/es_cpu.png> > > > 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: > https://gist.github.com/Kaidence/2b95c207f4e6a79841c5. > > 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66851a83-f5ca-4a52-becc-37a8b5052ef1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
