# Long gc pause happened on es1.7.0 plus jdk8u40

**URL:** <https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949>\
**Category:** Elasticsearch\
**Created:** [October 10, 2015, 8:42am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949 "2015-10-10T08:42:02Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 10, 2015, 8:42am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/1 "2015-10-10T08:42:02Z")

</div>

22042 2015-10-10T10:36:44.751+0800: 1954567.631: [GC (Allocation Failure) 1954567.631: [ParNew: 1606667K-\>41270K(1763584 K), 1221.6222148 secs] 5895406K-\>4332232K(16581312K), 1221.6230128 secs] [Times: user=11780.20 sys=0.00, real=1221 .44 secs]

is it a jdk bug or how to avoid it?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 11, 2015, 2:10am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/2 "2015-10-11T02:10:02Z")

</div>

How much data in your cluster, how much heap?

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 12, 2015, 2:27am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/3 "2015-10-12T02:27:54Z")

</div>

doc count: 4,695,567  
index siez:4.7GB(primary shard + replicas)  
index setting:  
"number\_of\_shards": "10"  
"number\_of\_replicas": "1"  
node count: 4  
heap commited: 30GB

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 12, 2015, 2:28am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/4 "2015-10-12T02:28:50Z")

</div>

please help to give suggestions

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 12, 2015, 7:08am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/5 "2015-10-12T07:08:59Z")

</div>

can anyone give any insight about this? I really bothers us a lot

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [October 12, 2015, 7:21am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/6 "2015-10-12T07:21:59Z")

</div>

A bit more information around the issue would be useful:

- Did the long GC affect one or all nodes?
- What does the workload look like?
- What type of hardware are the nodes deployed on?
- Is there anything else running on the host(s)?
- Has swap been disabled?

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 12, 2015, 7:53am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/7 "2015-10-12T07:53:04Z")

</div>

Which version of Elasticsearch and Java are you using?  
[answer]as mentioned in the title: es1.7.0 and jdk8u40  
Did the long GC affect one or all nodes?  
[answer]only one node  
What does the workload look like?  
[answer]write with 500tps and search with 300tps  
What type of hardware are the nodes deployed on?  
[answer]256GB ram, 32 core Xeon 2.6GHZ, 1TB spin disk  
Is there anything else running on the host(s)?  
[answer]Yes, there is another ES instance with same memory config running on that machine  
Has swap been disabled?  
[answer]yes.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 12, 2015, 8:18am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/8 "2015-10-12T08:18:03Z")

</div>

Are you using parent/child at all?

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 12, 2015, 8:43am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/9 "2015-10-12T08:43:07Z")

</div>

no, not at all

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 12, 2015, 9:08am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/10 "2015-10-12T09:08:36Z")

</div>

no, not at all

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 13, 2015, 1:05am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/11 "2015-10-13T01:05:21Z")

</div>

can anyone give any insight about this?

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 14, 2015, 3:57am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/12 "2015-10-14T03:57:07Z")

</div>

can you give any insights about this issue? I know it is tough issue, but u guys are exports

---

<div class="post-metadata">

**Author:** ![tinle](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tinle](https://discuss.elastic.co/u/tinle)\
**Post date:** [October 14, 2015, 4:22am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/13 "2015-10-14T04:22:50Z")

</div>

How many shards total for your cluster (primary and replica)?

Tin

---

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [October 14, 2015, 9:41am UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/14 "2015-10-14T09:41:41Z")

</div>

26 primary and 26 replica. total 52 shards.

---

<div class="post-metadata">

**Author:** ![tinle](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tinle](https://discuss.elastic.co/u/tinle)\
**Post date:** [October 14, 2015, 6:10pm UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/15 "2015-10-14T18:10:40Z")

</div>

You mentioned 300tps for search. What does your fielddata metrics look like?

You can get that from curl -s localhost:9200/\_cluster/stats

Could be your queries are using up the heap.

---

<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 5, 2017, 11:44pm UTC](https://discuss.elastic.co/t/long-gc-pause-happened-on-es1-7-0-plus-jdk8u40/31949/16 "2017-07-05T23:44:50Z")

</div>


