I received an email from Linode saying my instance had been using high CPU
and sure enough a java process was running between 22) - 280% CPU. Stopping
elasticsearch with rcelasticsearch stop removed the java process.
As soon as I do rcelasticsearch start again the java process appears using
the same CPU level. Have had to stop it for now.
That was with v0.19.4 so I upgraded to 0.19.8 but got the same problem.
Am using Ubuntu 10.04.1 LTS.
Anyone have any ideas?
I'm not all too familiar with advanced command line linux so if you need
any more info am glad to help but please let me know what commands to run!
Thanks
Also forgot to mention I have run the leap second fix mentioned on the
forums, to no avail
On Tuesday, July 3, 2012 12:06:11 AM UTC+1, Charlie wrote:
I received an email from Linode saying my instance had been using high CPU
and sure enough a java process was running between 22) - 280% CPU. Stopping
elasticsearch with rcelasticsearch stop removed the java process.
As soon as I do rcelasticsearch start again the java process appears using
the same CPU level. Have had to stop it for now.
That was with v0.19.4 so I upgraded to 0.19.8 but got the same problem.
Am using Ubuntu 10.04.1 LTS.
Anyone have any ideas?
I'm not all too familiar with advanced command line linux so if you need
any more info am glad to help but please let me know what commands to run!
Thanks
Weird, just tried the leap second trick again (while elasticsearch was
running this time) and seems to have worked for now. Is the leap second
command a one-off thing?
On Tuesday, July 3, 2012 12:06:44 AM UTC+1, Charlie wrote:
Also forgot to mention I have run the leap second fix mentioned on the
forums, to no avail
On Tuesday, July 3, 2012 12:06:11 AM UTC+1, Charlie wrote:
I received an email from Linode saying my instance had been using high
CPU and sure enough a java process was running between 22) - 280% CPU.
Stopping elasticsearch with rcelasticsearch stop removed the java process.
As soon as I do rcelasticsearch start again the java process appears
using the same CPU level. Have had to stop it for now.
That was with v0.19.4 so I upgraded to 0.19.8 but got the same problem.
Am using Ubuntu 10.04.1 LTS.
Anyone have any ideas?
I'm not all too familiar with advanced command line linux so if you need
any more info am glad to help but please let me know what commands to run!
Thanks