Elasticsearch 8.14 Upgrade: Resource Already exists exception

Elastic Stack Elasticsearch
1

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.

[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

[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]]
2

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?

3

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 :slight_smile:

4

Anything logged at DEBUG is not log pollution. Please see these docs 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.

1 Like