Not updating settings for the index because upgraded of some primary shards failed expected; received – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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 expected; received ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, index, indices, settings and shards.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Not updating settings for the index [{}] because upgraded of some primary shards failed – expected[{}]; received[{}]” 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);




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content