# Elastic keeps creating indices with replica:1

**URL:** https://discuss.elastic.co/t/elastic-keeps-creating-indices-with-replica-1/325390
**Category:** Elasticsearch
**Created:** [February 13, 2023, 2:30pm UTC](https://discuss.elastic.co/t/elastic-keeps-creating-indices-with-replica-1/325390 "2023-02-13T14:30:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![martijnomoda](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@martijnomoda](https://discuss.elastic.co/u/martijnomoda)
#### Post date: [February 13, 2023, 2:30pm UTC](https://discuss.elastic.co/t/elastic-keeps-creating-indices-with-replica-1/325390/1 "2023-02-13T14:30:45Z")

</div>

I have an cloud Elastic cluster with 1 hot node and 1 cold node. Because of this, I limited my replica to 0 when an index has been created. I have done this trough a index template with a high prioritity (99999), with the following settings.

```auto
{
  "index": {
    "number_of_shards": "1",
    "number_of_replicas": "0"
  }
}

```

However, everytime I clean up the indices with replica: 1, everyday new indices are being created with a replica: 1. How can I prevent this?

I also get this warning in Elastic search:

```auto
Searches might be slower than usual. Fewer redundant copies of the data exist on 45 indices [.ds-traces-apm-default-2023.02.12-000357, .ds-traces-apm-default-2023.02.13-000360, .ds-traces-apm-default-2023.02.13-000361, .ds-filebeat-8.3.2-2023.02.11-000231, .ds-filebeat-8.3.2-2023.02.12-000232, .ds-logs-elastic_agent-default-2023.02.12-000047, .ds-logs-elastic_agent-default-2023.02.13-000048, .ds-logs-elastic_agent.filebeat-default-2023.02.12-000015, .ds-logs-elastic_agent.filebeat-default-2023.02.13-000016, .ds-logs-elastic_agent.metricbeat-default-2023.02.10-000005, ...].

```

---

<div class="post-metadata">

### 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: [February 14, 2023, 4:35am UTC](https://discuss.elastic.co/t/elastic-keeps-creating-indices-with-replica-1/325390/2 "2023-02-14T04:35:03Z")

</div>

Welcome to our community! 😃

I would be looking to see if you have a template that matches that index pattern that has a different replica number sent, as a specific template will take priority over a generalised one, even one with a higher priority.

---

<div class="post-metadata">

### Author: ![martijnomoda](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@martijnomoda](https://discuss.elastic.co/u/martijnomoda)
#### Post date: [February 14, 2023, 9:26am UTC](https://discuss.elastic.co/t/elastic-keeps-creating-indices-with-replica-1/325390/3 "2023-02-14T09:26:01Z")

</div>

Thanks for your welcome and reply.

I have looked into this, but can't seem to find another index template that has a better match than this. For example, this index won't rollover:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/e/3ef640d079df7b7362e157bdbc066125ad0abc1e.png)

And this is my index template overview:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/4/04c78d52971404beb8b03b819970ff38151dcd83.png)

what strikes me is that this only happens with .ds indexes. The other ones rollover fine from hot to cold.

---

<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 14, 2023, 9:26am UTC](https://discuss.elastic.co/t/elastic-keeps-creating-indices-with-replica-1/325390/4 "2023-03-14T09:26:39Z")

</div>

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