# Indices.store.throttle.type: none and max\_bytes\_per\_sec (ES 1.7.x), should I raise max\_bytes\_per\_sec on RAID? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 22, 2016, 3:29pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125 "2016-03-22T15:29:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\ **Post date:** [March 22, 2016, 3:29pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125/1 "2016-03-22T15:29:35Z")
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\_bytes\_per\_sec still impact the merge rate? If I tweak the max\_bytes\_per\_sec value, it shows it defaulting to a very low 20MB/s. If so, might I see a reduction in index throttling if I raise the max\_bytes\_per\_sec to something higher? ---
**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\ **Post date:** [March 24, 2016, 4:47pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125/2 "2016-03-24T16:47:28Z")
Closest reference I've found so far ... [Excessive merging/small segment sizes](https://discuss.elastic.co/t/excessive-merging-small-segment-sizes/18491) ---
**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\ **Post date:** [March 25, 2016, 8:40pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125/3 "2016-03-25T20:40:22Z")
I've (tried) to read through some of the ES code (StoreRateLimiting,RateLimitedFSDirectory) and into some Lucene code (SimpleRateLimiter) and my interpretation is that the rate limitation is not in effect if the merge type is set to none. Does this sound right? ---
**Author:** ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)\ **Post date:** [March 25, 2016, 10:04pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125/4 "2016-03-25T22:04:14Z")
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 ---
**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\ **Post date:** [March 28, 2016, 1:09pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125/5 "2016-03-28T13:09:24Z")
Thanks, this confirmation is helpful! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:04pm UTC](https://discuss.elastic.co/t/indices-store-throttle-type-none-and-max-bytes-per-sec-es-1-7-x-should-i-raise-max-bytes-per-sec-on-raid/45125/6 "2017-07-05T23:04:43Z")