I have elasticsearch installed on a AWS box. I am doing some testing
with it. Indexing like 3K records. All text. I kick off an indexing
with Elastica and after about 15 seconds JAVA goes to 100% CPU.
Memory is consistant at about 37%
It's a micro box and I have the following configs and settings
Elastic Search 0.18.5
ES_MIN and ES_MAX 256 - 300
Using the Elasticsearch service wrapper
bootstrap.mlockall: true
java version "1.6.0_20"
I'm just looking for figure out how to not make java take up 100 % of
the CPU.
If you stop indexing, does the CPU go down? Maybe its just the load of the
indexing that takes all that CPU on the micro instance (which is, well,
micro ).
I have elasticsearch installed on a AWS box. I am doing some testing
with it. Indexing like 3K records. All text. I kick off an indexing
with Elastica and after about 15 seconds JAVA goes to 100% CPU.
Memory is consistant at about 37%
It's a micro box and I have the following configs and settings
Elastic Search 0.18.5
ES_MIN and ES_MAX 256 - 300
Using the Elasticsearch service wrapper
bootstrap.mlockall: true
java version "1.6.0_20"
I'm just looking for figure out how to not make java take up 100 % of
the CPU.
On Wed, Dec 21, 2011 at 7:48 PM, Shay Banon kimchy@gmail.com wrote:
If you stop indexing, does the CPU go down? Maybe its just the load of the
indexing that takes all that CPU on the micro instance (which is, well,
micro ).
Indeed, from my experience with micro instances, you can get up to 2
EC units of computing power in "burst mode" for a few seconds, with
the CPU then being completely starved for the next several seconds.
(to the point that the machine won't even respond to ping, actually)
My suggestion for the original poster would be to try using a small
instance instead. You'll get 1 EC compute unit with that, but you can
use the CPU at 100% without any sort of throttling like what the micro
instances have.
From my experience it's the JVM which is really unhappy on the micro
instances as I had a similar problem when using HBase. I've tried even
creating it as a small and returning it to a micro but had same
problem.
I'm currently using a small EC2 instance which works fine. When under
heavy load it does go up-to 100% but behaves like a normal box.
On Wed, Dec 21, 2011 at 7:48 PM, Shay Banon kim...@gmail.com wrote:
If you stop indexing, does the CPU go down? Maybe its just the load of the
indexing that takes all that CPU on the micro instance (which is, well,
micro ).
Indeed, from my experience with micro instances, you can get up to 2
EC units of computing power in "burst mode" for a few seconds, with
the CPU then being completely starved for the next several seconds.
(to the point that the machine won't even respond to ping, actually)
My suggestion for the original poster would be to try using a small
instance instead. You'll get 1 EC compute unit with that, but you can
use the CPU at 100% without any sort of throttling like what the micro
instances have.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
).