# Is it possible for one index to use total index buffer for indexing? **URL:** \ **Category:** Elasticsearch\ **Created:** [December 15, 2015, 6:40am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198 "2015-12-15T06:40:38Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 15, 2015, 6:40am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/1 "2015-12-15T06:40:38Z")
Let's say I have a daily build index and each day, the document will only put into today's index while no data will be indexed into old index. it is possible for today's index occupy the total index buffer for indexintg action? if yes, dose it need additional manually operation? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 17, 2015, 12:35am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/2 "2015-12-17T00:35:32Z")
Possible, yes. What manual operation are you talking about? ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 17, 2015, 1:19am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/3 "2015-12-17T01:19:00Z")
I mean do I need to set some config or invoke some API manually to achieve so? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 17, 2015, 1:21am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/4 "2015-12-17T01:21:03Z")
No, it has a level of total memory it can use and you should let it manage that by itself. ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 17, 2015, 2:04am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/5 "2015-12-17T02:04:48Z")
then under what condition "today's index" will occupy all of indexing buffer ? ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [December 17, 2015, 2:35am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/6 "2015-12-17T02:35:27Z")
> [@makeyang](#): > > then under what condition "today's index" will occupy all of indexing buffer ? The indexing buffer is shared equally between all the indexes being actively written to. The check is every 30 seconds or so. So if no other indexes are being written to then your daily index should get the whole buffer. ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 17, 2015, 2:47am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/7 "2015-12-17T02:47:41Z")
I met a problem which traped me: I setup a cluster which is write heavy and it write daily index, whic means I create a index named today's date, like 2015-12-17 and today only write to this index. I set indices.memory.index\_buffer\_size to 20% for each node. At the beginning, the server run's very will. the index performance is met our write requirement. but after days, there will be bulk index rejection happens. So I thought it could be other index occupy index buffer and make today's index performance slow. but based on u guys comment, it turns out performance degression is not caused by indexing buffer. but then what caused? ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 17, 2015, 3:23am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/8 "2015-12-17T03:23:41Z")
or is there a way to lock this indexing buffer in case it is occupied by other things? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 17, 2015, 4:10am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/9 "2015-12-17T04:10:09Z")
Maybe your cluster is overloaded in general? Are you monitoring things? ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 17, 2015, 5:18am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/10 "2015-12-17T05:18:45Z")
I used ES2.1 plus marvel nothing is overloaded ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 17, 2015, 5:26am UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/11 "2015-12-17T05:26:49Z")
can you describe indices.memory.index\_buffer\_size indices.memory.min\_index\_buffer\_size indices.memory.max\_index\_buffer\_size indices.memory.min\_shard\_index\_buffer\_size internally working logic? ---
**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:30pm UTC](https://discuss.elastic.co/t/is-it-possible-for-one-index-to-use-total-index-buffer-for-indexing/37198/12 "2017-07-05T23:30:20Z")