Hello, My Elasticsearch stops to index when after certain number of logs are sent to elastic via logstash and I keep seeing [2018-03-08T15:44:34,677][INFO ][o.e.m.j.JvmGcMonitorService] [aTs5egi] [gc][14522] overhead, spent [460ms] collecting in the last [1s] 2018-03-08T15:44:35.562-0800 ERROR lo…

whicter (Viktor) March 9, 2018, 6:13pm 7

10G allocated for heap

Topic		Replies	Views
Gc overhead while index data using logstash Elasticsearch	7	1293	April 19, 2019
Logstash limitting ElasticSearch heap Elasticsearch	5	459	July 6, 2017
Indexing in Elasticsearch stops after particular number Elasticsearch	11	2391	December 6, 2017
Gc overhead, spent [] collecting in the last [], causing crashes Elasticsearch	22	20623	April 20, 2020
OutOfMemory exception after few hours of indexing Elasticsearch	6	1901	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Indexing stops at low number of records due to GC overhead with proper heap settings

Related topics