# Constant GC warnings with small indexes

**URL:** https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433
**Category:** Elasticsearch
**Created:** [November 4, 2021, 3:59pm UTC](https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433 "2021-11-04T15:59:19Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![lesleyr1](https://avatars.discourse-cdn.com/v4/letter/l/a88e4f/32.png) [@lesleyr1](https://discuss.elastic.co/u/lesleyr1)
#### Post date: [November 4, 2021, 3:59pm UTC](https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433/1 "2021-11-04T15:59:19Z")

</div>

Hello everyone,

My team is getting constant GC overhead warnings on our production Elasticsearch cluster for our Liferay application, at least 5 times each minute. This occurs any time, not just when reindexing.  
` "message": "[gc][665978] overhead, spent [986ms] collecting in the last [1s]",`

Here are our stats:  
**OS:** Amazon linux 2  
**Ram:** 32 gb  
**Heap:** 20 gb  
**Disk:** 90gb  
**Java version:** 8 ES  
**Elasticsearch version:** 7.4.2

I have made a [gist](https://gist.github.com/AWG-LesleyR/66ced30497519607d6497395f036df51) with the output of the cluster stats API.

We are very confused because our indexes are not very large and we avoid expensive queries.

We were wondering if anyone had any tips or thoughts on this.

Thanks very much!

---

<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: [November 4, 2021, 11:19pm UTC](https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433/2 "2021-11-04T23:19:27Z")

</div>

Welcome to our community! 😃

7.4 is [EOL](https://www.elastic.co/support/eol), please upgrade.

> [@lesleyr1](#):
>
> I have made a [gist](https://gist.github.com/AWG-LesleyR/66ced30497519607d6497395f036df51) with the output of the cluster stats API.

That doesn't look like the output I'd expect to see from that API. There's no information about the nodes, JVM or OS.

---

<div class="post-metadata">

### Author: ![lesleyr1](https://avatars.discourse-cdn.com/v4/letter/l/a88e4f/32.png) [@lesleyr1](https://discuss.elastic.co/u/lesleyr1)
#### Post date: [November 11, 2021, 11:00pm UTC](https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433/3 "2021-11-11T23:00:07Z")

</div>

Thanks for your response! We've been working on updating our test environment to the latest ES version. It doesn't seem to have helped this problem but it's definitely something we worth doing, we will get that going on prod soon.

Sorry about the gist, not sure what happened there, [here](https://gist.github.com/AWG-LesleyR/08b872c59468cfad5c90f36d3945a65f) is an accurate version if anyone has time to take a peek, they are from prod so the version upgrade won't be there yet.

Thanks again!

---

<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: [November 12, 2021, 6:15am UTC](https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433/4 "2021-11-12T06:15:10Z")

</div>

Is there anything else running on the host where Elasticsearch is running? Do you have swap enabled?

---

<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: [December 10, 2021, 6:15am UTC](https://discuss.elastic.co/t/constant-gc-warnings-with-small-indexes/288433/5 "2021-12-10T06:15:56Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.