# Elasticsearch 8.14 Upgrade: Resource Already exists exception

**URL:** <https://discuss.elastic.co/t/elasticsearch-8-14-upgrade-resource-already-exists-exception/364765>\
**Category:** Elasticsearch\
**Created:** [August 12, 2024, 8:15am UTC](https://discuss.elastic.co/t/elasticsearch-8-14-upgrade-resource-already-exists-exception/364765 "2024-08-12T08:15:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abhishek\_Soni1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhishek_soni1/32/108968_2.png) [@Abhishek\_Soni1](https://discuss.elastic.co/u/Abhishek_Soni1)\
**Post date:** [August 12, 2024, 8:15am UTC](https://discuss.elastic.co/t/elasticsearch-8-14-upgrade-resource-already-exists-exception/364765/1 "2024-08-12T08:15:25Z")

</div>

Hi I am trying to upgrade elasticsearch from 7.17 to 8.14.3, during upgrade, I found these exceptions, I don't know how to solve it.

```auto
[2024-08-12T03:31:11,986][DEBUG][o.e.a.s.m.TransportMasterNodeAction] [achillelheel01] unexpected exception during publication
org.elasticsearch.ResourceAlreadyExistsException: index [.slo-observability.summary-v3.2/j7Yp4G_sROSeYorhPYe1xA] already exists
        at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.validateIndexName(MetadataCreateIndexService.java:177) ~[elasticsearch-8.14.3.jar:?]
        at org.elasticsearch.cluster.metadata.MetadataCreateIndexService.validate(MetadataCreateIndexService.java:1371) ~[elasticsearch-8.14.3.jar:?]

```

And also

```auto
[2024-08-12T04:05:51,678][DEBUG][o.e.a.d.a.DataStreamAutoShardingService] [achillelheel01] Data stream auto sharding service is not enabled.
[2024-08-12T04:05:51,678][DEBUG][o.e.a.a.i.r.TransportRolloverAction] [achillelheel01] auto sharding result for data stream [ilm-history-7] is [AutoShardingResult[type=NOT_APPLICABLE, currentNumberOfShards=-1, targetNumberOfShards=-1, coolDownRemaining=106751.9d, writeLoad=null]]

```

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [August 12, 2024, 8:33am UTC](https://discuss.elastic.co/t/elasticsearch-8-14-upgrade-resource-already-exists-exception/364765/2 "2024-08-12T08:33:55Z")

</div>

Those aren't errors - they're debug logs, intended for engineers troubleshooting problems.  
You shouldn't need to turn on debug logging unless you are trying to debug a problem.

Has something failed during your upgrade?

---

<div class="post-metadata">

**Author:** ![Abhishek\_Soni1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhishek_soni1/32/108968_2.png) [@Abhishek\_Soni1](https://discuss.elastic.co/u/Abhishek_Soni1)\
**Post date:** [August 12, 2024, 9:12am UTC](https://discuss.elastic.co/t/elasticsearch-8-14-upgrade-resource-already-exists-exception/364765/3 "2024-08-12T09:12:12Z")

</div>

No, There is no failures, thanks for the great work by the elastic team.

Can we not remove these exceptions, If I want to keep debug logs on. It usually helps me a lot, during troubleshooting.

These logs are at many places in the logs, causing log pollution, if we can somehow get rid of them, it would be great 🙂

---

<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:** [August 12, 2024, 9:34am UTC](https://discuss.elastic.co/t/elasticsearch-8-14-upgrade-resource-already-exists-exception/364765/4 "2024-08-12T09:34:17Z")

</div>

> [@Abhishek\_Soni1](#):
>
> causing log pollution

Anything logged at `DEBUG` is not log pollution. Please see [these docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html#configuring-logging-levels) for more information:

> Do not enable logging at levels `DEBUG` or `TRACE` unless you are following instructions elsewhere in this manual which call for more detailed logging, or you are an expert user who will be reading the Elasticsearch source code to determine the meaning of the logs.