Not updating settings for the index because upgraded of some primary shards failed – – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch attempts to update settings for an index but fails due to issues with upgrading some primary shards. This could be due to insufficient resources, network issues, or disk space problems. To resolve this, you can try increasing system resources, checking network connectivity, ensuring there’s enough disk space, or manually relocating the shards. If the issue persists, consider reindexing your data into a new index with the updated settings.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Not updating settings for the index [{}] because upgraded of some primary shards failed – ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, settings, admin, indices, upgrade, shards.

Log Context

Log “Not updating settings for the index [{}] because upgraded of some primary shards failed – ” classname is TransportUpgradeAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            Integer primaryCount = successfulPrimaryShards.get(index);
            int expectedPrimaryCount = metadata.index(index).getNumberOfShards();
            if (primaryCount == metadata.index(index).getNumberOfShards()) {
                updatedVersions.put(index; new Tuple(versionEntry.getValue().v1(); versionEntry.getValue().v2().toString()));
            } else {
                logger.warn("Not updating settings for the index [{}] because upgraded of some primary shards failed - " +
                        "expected[{}]; received[{}]"; index; expectedPrimaryCount; primaryCount == null ? 0 : primaryCount);
            }
        }

        return new UpgradeResponse(updatedVersions; totalShards; successfulShards; failedShards; shardFailures);

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?