Slow Commands with 1.2.4 to 1.4.2 Upgrade

Elastic Stack Elasticsearch
1

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 and _nodes.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

How slow?
Is the load on your system high?

On 31 December 2014 at 05:04, pskieu@gmail.com wrote:

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 and _nodes.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_6dPyKpiX_vrTnvybOoYLEOcKG5jatVtjy4SVht87fMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

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, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1286f276-e20c-4ff2-acc0-90a5a3d57b0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

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 December 2014 at 05:04, <psk...@gmail.com <javascript:>> wrote:

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 and _nodes.

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f9ab96bf-b5c3-4f99-9c9c-e00568aada9c%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9e3f7c4b-0705-4063-a591-8c5359ff8254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

5

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:12 PM UTC+1, psk...@gmail.com wrote:

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, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2c48b2b5-f2a1-41bd-b7f0-d4042fc147cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

6

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:12 PM UTC+1, psk...@gmail.com wrote:

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, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c163ad96-23df-435f-a2a0-ae82687039a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

7

With 32GB of memory this should be around 16GB (50%), and check if this
actually is the case with top for example.

On Friday, January 16, 2015 at 6:52:02 PM UTC+1, psk...@gmail.com wrote:

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:12 PM UTC+1, psk...@gmail.com wrote:

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, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/44c7b87f-f87c-4e2f-9c11-2cbc2ca0167f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

8

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
actually is the case with top for example.

On Friday, January 16, 2015 at 6:52:02 PM UTC+1, psk...@gmail.com wrote:

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:12 PM UTC+1, psk...@gmail.com wrote:

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, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/65e8ea85-f9fb-4315-a90c-7f14c17385b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

9

Do you have a firewall between you and the cluster?
What sort of times does a ping response show you?
Have you looked at your ES logs, hot threads?

On 21 January 2015 at 14:51, pskieu@gmail.com wrote:

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
actually is the case with top for example.

On Friday, January 16, 2015 at 6:52:02 PM UTC+1, psk...@gmail.com wrote:

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:12 PM UTC+1, psk...@gmail.com wrote:

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, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/65e8ea85-f9fb-4315-a90c-7f14c17385b9%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/65e8ea85-f9fb-4315-a90c-7f14c17385b9%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8WZfiwt1wsH4UNvOHTp7naByiJt0bE2Lw1Ba0yU2BAxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.