# Reasons for not using G1 GC?

**URL:** <https://discuss.elastic.co/t/reasons-for-not-using-g1-gc/110853>\
**Category:** Elasticsearch\
**Created:** [December 8, 2017, 1:41pm UTC](https://discuss.elastic.co/t/reasons-for-not-using-g1-gc/110853 "2017-12-08T13:41:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeroen1](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@jeroen1](https://discuss.elastic.co/u/jeroen1)\
**Post date:** [December 8, 2017, 1:41pm UTC](https://discuss.elastic.co/t/reasons-for-not-using-g1-gc/110853/1 "2017-12-08T13:41:28Z")

</div>

Using G1 GC for Elasticsearch was discouraged. As far as I can see the main argument was instability / buggy G1 code (see older Java changelogs). Nowadays G1 seems to be solid.

Are there good reasons nowadays for NOT using Java 8 with G1 in ES6? Thanks!

---

<div class="post-metadata">

**Author:** ![dmitriy\_o](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dmitriy_o/32/23370_2.png) [@dmitriy\_o](https://discuss.elastic.co/u/dmitriy_o)\
**Post date:** [December 12, 2017, 8:18am UTC](https://discuss.elastic.co/t/reasons-for-not-using-g1-gc/110853/2 "2017-12-12T08:18:24Z")

</div>

```auto
support the issue

```

---

<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:** [January 9, 2018, 8:18am UTC](https://discuss.elastic.co/t/reasons-for-not-using-g1-gc/110853/3 "2018-01-09T08:18:29Z")

</div>

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