# Prevent co-placement of daily heavy-duty indices

**URL:** <https://discuss.elastic.co/t/prevent-co-placement-of-daily-heavy-duty-indices/218432>\
**Category:** Elasticsearch\
**Created:** [February 8, 2020, 10:23am UTC](https://discuss.elastic.co/t/prevent-co-placement-of-daily-heavy-duty-indices/218432 "2020-02-08T10:23:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Niteshade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niteshade/32/27825_2.png) [@Niteshade](https://discuss.elastic.co/u/Niteshade)\
**Post date:** [February 8, 2020, 10:23am UTC](https://discuss.elastic.co/t/prevent-co-placement-of-daily-heavy-duty-indices/218432/1 "2020-02-08T10:23:03Z")

</div>

Hi  
We operate a \>100 nodes cluster, the size mainly intended to allow requests on a big temporal depth.  
We are daily creating a few separate indices for indexing ( up to ten shard per indice + replicas ).  
We notice that shards from these different indices are often allocated to the same node, leading to high resources contention.

Indices are created at the same hour ( midnight).  
Any idea how we can have allocation to separate nodes ?

P.s. of course we have limited to 1 shard per node these indices...

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 8, 2020, 10:41am UTC](https://discuss.elastic.co/t/prevent-co-placement-of-daily-heavy-duty-indices/218432/2 "2020-02-08T10:41:38Z")

</div>

Hi Cedric, and welcome.

If you don't want particular indices to be co-located then the simplest solution is to define the sets of nodes for each index up-front, using [node attributes and shard allocation filtering](https://www.elastic.co/guide/en/elasticsearch/reference/current/shard-allocation-filtering.html#index-allocation-filters).

It's not unusual to only want to apply this restriction while the index is actively writing documents. If so, you can remove the allocation filter once the next index becomes active.

---

<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:** [March 7, 2020, 10:41am UTC](https://discuss.elastic.co/t/prevent-co-placement-of-daily-heavy-duty-indices/218432/3 "2020-03-07T10:41:48Z")

</div>

Closed on March 7, 2020, 10:41am UTC

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