I'm having issues with merge throttling indexing. Setting "indices.store.throttle.type" to "none" doesn't seem to prevent throttling if max_merge_count is exceeded. I don't have SSDs, but the server that I am using has RAID which has a 1200MB/s throughput. If I set throttle type to none, does max_…

unknownunknown, That is correct. with indices.store.throttle.type set to none, any value for indices.store.throttle.max_bytes_per_sec is not used. Glen

Discuss the Elastic Stack

Indices.store.throttle.type: none and max_bytes_per_sec (ES 1.7.x), should I raise max_bytes_per_sec on RAID?

Elastic Stack Elasticsearch

unknownunknown March 24, 2016, 4:47pm 2

Closest reference I've found so far ... Excessive merging/small segment sizes

Topic		Replies	Views
Reduce Number of Segments Elasticsearch	8	1319	July 6, 2017
Tiered merge policy settings not documented in 2.x: gone? Elasticsearch	3	1168	July 5, 2017
Optimize elasticsearch segment merge Elasticsearch	5	1579	May 1, 2020
Maximize read/write throughput Elasticsearch	11	7126	October 1, 2019
Elasticsearch Segment Size Elasticsearch	18	7713	July 5, 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.

Indices.store.throttle.type: none and max_bytes_per_sec (ES 1.7.x), should I raise max_bytes_per_sec on RAID?

Related Topics