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

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
Throttling merges despite indices.store.throttle.type: none Elasticsearch	1	970	December 1, 2017
Merging and indices.store.throttle.max_bytes_per_sec Elasticsearch	1	742	November 27, 2017
Indices.store.throttle.max_bytes_per_sec config setting and 2.2 Elasticsearch	3	2269	July 5, 2017
Updating indices.store.throttle.max_bytes_per_sec from [10gb]? Elasticsearch	4	1505	July 5, 2017
ES 2.4 indices.store.throttle settings with SSD servers Elasticsearch	2	1399	July 5, 2017

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