# G1GC In Production with Regard to Consistency

**URL:** https://discuss.elastic.co/t/g1gc-in-production-with-regard-to-consistency/47561
**Category:** Elasticsearch
**Created:** [April 16, 2016, 11:45am UTC](https://discuss.elastic.co/t/g1gc-in-production-with-regard-to-consistency/47561 "2016-04-16T11:45:57Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![rusty](https://avatars.discourse-cdn.com/v4/letter/r/f17d59/32.png) [@rusty](https://discuss.elastic.co/u/rusty)
#### Post date: [April 16, 2016, 12:43pm UTC](https://discuss.elastic.co/t/g1gc-in-production-with-regard-to-consistency/47561/2 "2016-04-16T12:43:48Z")

</div>

Please take a look at our experience with G1GC ([link](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/16)) and some related issue in the same topic ([link] ([Indexing performance degrading over time](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/59))). This is not data corruption but other strange side effect of this GC. As for us we switched back to CMS and the problem with overload node gone.

---

_[View the full topic](https://discuss.elastic.co/t/g1gc-in-production-with-regard-to-consistency/47561)._