# ES 6.8.23 too many Full GC **URL:** \ **Category:** Elasticsearch\ **Created:** [August 19, 2022, 2:37pm UTC](https://discuss.elastic.co/t/es-6-8-23-too-many-full-gc/312478 "2022-08-19T14:37:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Andrey\_Tyutyunov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrey_tyutyunov/32/98571_2.png) [@Andrey\_Tyutyunov](https://discuss.elastic.co/u/Andrey_Tyutyunov)\ **Post date:** [August 19, 2022, 2:37pm UTC](https://discuss.elastic.co/t/es-6-8-23-too-many-full-gc/312478/1 "2022-08-19T14:37:51Z")
Good day! Version 6.8.23 3 nodes, 26GB heap per node, 64GB RAM on each node java 14 Indices: 49 Documents 516,257,116 Disk Usage 872.0 GB Primary Shards 165 Replica Shards 165 Search Rate (/s) ~ 750 /s (total shards) Indexing Rate (/s) ~ 200 /s (total shards) On garbage collector stat I see strange situation - too many cases Full GC, below Full GC on 2 hrs 24 min 10 sec ### Full GC stats | Full GC Count | 12328 | | --- | --- | | Full GC reclaimed | 7.81 gb | | Full GC total time | 40 sec 782 ms | | Full GC avg time | 3.31 ms | | Full GC avg time std dev | 2.60 ms | | Full GC min/max time | 0.466 ms / 15.6 ms | | Full GC Interval avg | 701 ms | It's okey? Looks very strange. I have no see any other problem, elasticsearch log without errors / warnings / causes, response time - search time - index time no any problems, CPU usage on any node 20-30%, each node on deducated server. ![Снимок экрана 2022-08-19 в 19.32.49](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1f470c0a3b3d07a0b362db6ed5a907a79e3c9cb8.jpeg) ![Снимок экрана 2022-08-19 в 19.32.42](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af353818d16a33148813f7207cc3de7dd7334cfe.jpeg) ---
**Author:** ![Andrey\_Tyutyunov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrey_tyutyunov/32/98571_2.png) [@Andrey\_Tyutyunov](https://discuss.elastic.co/u/Andrey_Tyutyunov)\ **Post date:** [August 19, 2022, 3:02pm UTC](https://discuss.elastic.co/t/es-6-8-23-too-many-full-gc/312478/2 "2022-08-19T15:02:44Z")
I think I found answer - this is look like bug in GC log visualizer for second rotated log, first gc log looks similar but all marks as Young GC, correct me please if I'm wrong ![Снимок экрана 2022-08-19 в 20.01.49](https://us1.discourse-cdn.com/elastic/original/3X/4/6/4623c62154bddaeac668d2ccf04b1169015732f5.jpeg) ---
**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:** [August 22, 2022, 12:29am UTC](https://discuss.elastic.co/t/es-6-8-23-too-many-full-gc/312478/3 "2022-08-22T00:29:53Z")
Your GC looks pretty good, it's running and cleaning heap as it should be. > [@Andrey\_Tyutyunov](#): > > Version 6.8.23 Please upgrade 6.8 is very much past [EOL](https://www.elastic.co/support/eol) and there have been numerous improvements in newer versions that will help your situationm ---
**Author:** ![Andrey\_Tyutyunov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrey_tyutyunov/32/98571_2.png) [@Andrey\_Tyutyunov](https://discuss.elastic.co/u/Andrey_Tyutyunov)\ **Post date:** [August 30, 2022, 3:55am UTC](https://discuss.elastic.co/t/es-6-8-23-too-many-full-gc/312478/4 "2022-08-30T03:55:31Z")
Thank you, upgrade in progress - the cluster uses in heavy load project as main store and need in refactor code and reorganize DB ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 27, 2022, 3:56am UTC](https://discuss.elastic.co/t/es-6-8-23-too-many-full-gc/312478/5 "2022-09-27T03:56:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.