# Why is ES indexing buffer coupled with lucene flush RAM buffer size?

**URL:** <https://discuss.elastic.co/t/why-is-es-indexing-buffer-coupled-with-lucene-flush-ram-buffer-size/173935>\
**Category:** Elasticsearch\
**Created:** [March 26, 2019, 1:12pm UTC](https://discuss.elastic.co/t/why-is-es-indexing-buffer-coupled-with-lucene-flush-ram-buffer-size/173935 "2019-03-26T13:12:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![itiyamas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itiyamas/32/44685_2.png) [@itiyamas](https://discuss.elastic.co/u/itiyamas)\
**Post date:** [March 26, 2019, 1:12pm UTC](https://discuss.elastic.co/t/why-is-es-indexing-buffer-coupled-with-lucene-flush-ram-buffer-size/173935/1 "2019-03-26T13:12:13Z")

</div>

One will end up creating a segment and another will trigger putting the segment to disk. The limit essentially denotes the amount of memory that we can afford for a particular shard in memory- which makes sense.

Is there any other reason to keep them the same? I am sorry but I could not find any documentation on this.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 23, 2019, 1:12pm UTC](https://discuss.elastic.co/t/why-is-es-indexing-buffer-coupled-with-lucene-flush-ram-buffer-size/173935/2 "2019-04-23T13:12:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.