Lowered to 16g and verified with top--same behavior. I've also tried 1.3
with the same results.
1.2 is the latest version that's working properly for me.
On Saturday, January 17, 2015 at 5:02:03 AM UTC-8, Arie wrote:
>
> With 32GB of memory this should be around 16GB (50%), and check if this
>
My ES_HEAP_SIZE is already set to 24g per node
On Friday, January 16, 2015 at 4:25:00 AM UTC-8, Arie wrote:
>
> Check your memory usage on ES. In my case I had to specifically put
> ES_HEAP_SIZE in /etc/init.d/elasticsearch
> to get it working the right way.
>
> On Monday, January 5, 2015 at 7:45
Just added 2 more nodes with the same specs, and still seeing the same
slowness. These commands no longer return anything, because it's taking too
long to return.
On Tuesday, December 30, 2014 at 3:54:34 PM UTC-8, Mark Walkom wrote:
>
> How slow?
> Is the load on your system high?
>
> On 31 Dec
It takes upwards an average of 10 to 30 seconds. This is a test instance, so
there's no additional load other than what I'm doing.
--
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
I have about 50 GB of data (1 mil docs) in a single node--8 cores with 32
GB (24 GB heap). I just upgraded from 1.2.4 to 1.4.2, and I noticed that a
few commands take a long time to return, and marvel doesn't work as well as
it used to.
Some of the commands that are slow for me are _cat/indices
I'm running a docker container with ES in it. The cluster works fine but I
keep getting warning messages about it trying to connect to itself.
[2014-06-30 18:26:21,105][WARN ][cluster.service ] [ES01] failed
to reconnect to node
[ES01][miTCM9-BQwmhlL4mk7EX1w][fb06cbd6bd18][inet[es-host
