{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/4288","labels_url":"https://api.github.com/repos/elastic/elasticsearch/issues/4288/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch/issues/4288/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch/issues/4288/events","html_url":"https://github.com/elastic/elasticsearch/issues/4288","id":23429444,"number":4288,"title":"ES java very high CPU usage","user":{"login":"ydnitin","id":3760080,"avatar_url":"https://avatars.githubusercontent.com/u/3760080?v=3","gravatar_id":"","url":"https://api.github.com/users/ydnitin","html_url":"https://github.com/ydnitin","followers_url":"https://api.github.com/users/ydnitin/followers","following_url":"https://api.github.com/users/ydnitin/following{/other_user}","gists_url":"https://api.github.com/users/ydnitin/gists{/gist_id}","starred_url":"https://api.github.com/users/ydnitin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ydnitin/subscriptions","organizations_url":"https://api.github.com/users/ydnitin/orgs","repos_url":"https://api.github.com/users/ydnitin/repos","events_url":"https://api.github.com/users/ydnitin/events{/privacy}","received_events_url":"https://api.github.com/users/ydnitin/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":{"login":"spinscale","id":667544,"avatar_url":"https://avatars.githubusercontent.com/u/667544?v=3","gravatar_id":"","url":"https://api.github.com/users/spinscale","html_url":"https://github.com/spinscale","followers_url":"https://api.github.com/users/spinscale/followers","following_url":"https://api.github.com/users/spinscale/following{/other_user}","gists_url":"https://api.github.com/users/spinscale/gists{/gist_id}","starred_url":"https://api.github.com/users/spinscale/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spinscale/subscriptions","organizations_url":"https://api.github.com/users/spinscale/orgs","repos_url":"https://api.github.com/users/spinscale/repos","events_url":"https://api.github.com/users/spinscale/events{/privacy}","received_events_url":"https://api.github.com/users/spinscale/received_events","type":"User","site_admin":false},"milestone":null,"comments":14,"created_at":"2013-11-28T04:02:46Z","updated_at":"2015-06-12T11:08:53Z","closed_at":"2014-02-22T16:13:56Z","body":"I am having similar issues as described on this thread. https://github.com/elasticsearch/elasticsearch/issues/1940\r\nAlthough leap second already happened in June but I tried resetting the time anyway. Didn't work. \r\nThis is causing a lot of frustration. Any help is much appreciated. \r\n\r\nI have upgraded ES to the latest (elasticsearch-0.90.7-1). Have restarted ES, front end, logstash. no joy at all. \r\n\r\njava -version\r\njava version \"1.7.0_45\"\r\nOpenJDK Runtime Environment (rhel-2.4.3.2.el6_4-x86_64 u45-b15)\r\nOpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)\r\n\r\nAfter the upgrade I am seeing these in the logs, which seems like a totally different issues. \r\n\r\n[2013-11-28 03:48:32,796][WARN ][discovery.zen            ] [LA Logger] received a join                    request for an existing node [[Night Thrasher][ecqZvZhDSTGiVkrjj6G_hw][inet[/192.168.1                   28.146:9300]]{client=true, data=false}]\r\n[2013-11-28 03:48:36,006][WARN ][discovery.zen            ] [LA Logger] received a join                    request for an existing node [[Night Thrasher][ecqZvZhDSTGiVkrjj6G_hw][inet[/192.168.1                   28.146:9300]]{client=true, data=false}]\r\n\r\nHot thread output: https://gist.github.com/ydnitin/7687098"},"comment":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/comments/111453868","html_url":"https://github.com/elastic/elasticsearch/issues/4288#issuecomment-111453868","issue_url":"https://api.github.com/repos/elastic/elasticsearch/issues/4288","id":111453868,"user":{"login":"ACV2","id":6947506,"avatar_url":"https://avatars.githubusercontent.com/u/6947506?v=3","gravatar_id":"","url":"https://api.github.com/users/ACV2","html_url":"https://github.com/ACV2","followers_url":"https://api.github.com/users/ACV2/followers","following_url":"https://api.github.com/users/ACV2/following{/other_user}","gists_url":"https://api.github.com/users/ACV2/gists{/gist_id}","starred_url":"https://api.github.com/users/ACV2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ACV2/subscriptions","organizations_url":"https://api.github.com/users/ACV2/orgs","repos_url":"https://api.github.com/users/ACV2/repos","events_url":"https://api.github.com/users/ACV2/events{/privacy}","received_events_url":"https://api.github.com/users/ACV2/received_events","type":"User","site_admin":false},"created_at":"2015-06-12T11:08:53Z","updated_at":"2015-06-12T11:08:53Z","body":"\r\nHey there, @Travis. Actually it was a journey... Elastic Search is everything but human friendly, after this post where I actually checked every single configuration trying to optimize the performance to avoid this behavior, with not success... I reduce the query time from 12 sec to 2-3 in a period of 10-15 minutes still huge and unacceptable, however we are working to optimize our back end to stabilize the performance, that being said.. My findings:\r\n\r\n-merge process\r\n-flush process\r\n-background process (script) bombarding the server with queries slowing it down \r\n\r\nCan you post your server configurations so I can help you a little bit more :)\r\n\r\nRegards\r\nDaniel \r\n> On 7/6/2015, at 16:27, Travis Bell <notifications@github.com> wrote:\r\n> \r\n> @AVC2 Did you learn anything since your post about this? We're seeing more or less, the same problem. Sometimes daily, sometimes only one a week (it's that random) one of our ES hosts decides to go crazy. We usually restart the instance when we see this because it affects our end users response times but it's starting to be a problem.\r\n> \r\n> I was just curious is you learned anything that could help point us in the right direction. I'll see about checking the hot threads output and slowlogs.\r\n> \r\n> —\r\n> Reply to this email directly or view it on GitHub.\r\n> \r\n"}}