# \[0.90.x\] Sorting stress test and no response

**URL:** https://discuss.elastic.co/t/0-90-x-sorting-stress-test-and-no-response/12234
**Category:** Elasticsearch
**Created:** [June 3, 2013, 12:54pm UTC](https://discuss.elastic.co/t/0-90-x-sorting-stress-test-and-no-response/12234 "2013-06-03T12:54:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Marek\_Skorek](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Marek\_Skorek](https://discuss.elastic.co/u/Marek_Skorek)
#### Post date: [June 3, 2013, 12:54pm UTC](https://discuss.elastic.co/t/0-90-x-sorting-stress-test-and-no-response/12234/1 "2013-06-03T12:54:14Z")

</div>

Hi,

I am testing the limitation for field data cache and I have met some  
problem.

The case is to execute 3 queries at the same time (nearly) with sorting as  
below:  
query1: sorting by 5 fields (3 of them are unique)  
query2: sorting by 1 field (1 unique of the 5 from query1)  
query3: sorting by 2 fields (2 non-unique of the 5 from query2; just en  
Enums/Strings - not too many distinct values)

The index size is about 115M docs that matches above queries.  
My cluster consists of 3 nodes with 1,5G of Heap (for test purposes only)  
and the field data cache size is set to 50% of node's heap.

After a while the "OOME: Java heap space" occurs on the node I request with  
curl.

Despite of above the cluster is still runing and responsive to queries but  
these 3 queries hangs up (no reponse sice 5 hours) and GC is going crazy on  
the node requested by these queries.

Is it normal behaviour or maybe I have missed something in my configuration?  
index.fielddata.cache: node  
indices.fielddata.cache.size: 50%

Attached Bigdesk screenshot from the node1.  
Other nodes seems to be ok (no OOME reported).

--  
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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![Marek\_Skorek](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Marek\_Skorek](https://discuss.elastic.co/u/Marek_Skorek)
#### Post date: [June 4, 2013, 6:25am UTC](https://discuss.elastic.co/t/0-90-x-sorting-stress-test-and-no-response/12234/2 "2013-06-04T06:25:12Z")

</div>

I have left my computer working for a night and the queries has got still  
no responses.

After killing curls commands the CPU usage is still about 100% (of 800%).  
Heap usage is still growing and GC is working all the time.

Addidional information about JVM:  
java version "1.7.0\_03"  
OpenJDK Runtime Environment (IcedTea7 2.1.7) (7u3-2.1.7-1)  
OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)

W dniu poniedziałek, 3 czerwca 2013 14:54:14 UTC+2 użytkownik Marek Skorek  
napisał:

> Hi,
> 
> I am testing the limitation for field data cache and I have met some  
> problem.
> 
> The case is to execute 3 queries at the same time (nearly) with sorting as  
> below:  
> query1: sorting by 5 fields (3 of them are unique)  
> query2: sorting by 1 field (1 unique of the 5 from query1)  
> query3: sorting by 2 fields (2 non-unique of the 5 from query2; just en  
> Enums/Strings - not too many distinct values)
> 
> The index size is about 115M docs that matches above queries.  
> My cluster consists of 3 nodes with 1,5G of Heap (for test purposes only)  
> and the field data cache size is set to 50% of node's heap.
> 
> After a while the "OOME: Java heap space" occurs on the node I request  
> with curl.
> 
> Despite of above the cluster is still runing and responsive to queries but  
> these 3 queries hangs up (no reponse sice 5 hours) and GC is going crazy on  
> the node requested by these queries.
> 
> Is it normal behaviour or maybe I have missed something in my  
> configuration?  
> index.fielddata.cache: node  
> indices.fielddata.cache.size: 50%
> 
> Attached Bigdesk screenshot from the node1.  
> Other nodes seems to be ok (no OOME reported).

--  
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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:33am UTC](https://discuss.elastic.co/t/0-90-x-sorting-stress-test-and-no-response/12234/3 "2017-07-06T02:33:09Z")

</div>


