Log Updating index.store.throttle.type from to – How To Solve Related Issues

Log Updating index.store.throttle.type from to – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0


Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Updating index.store.throttle.type from to ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “updating index.store.throttle.type from [{}] to [{}]” classname is IndexStore.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     class ApplySettings implements IndexSettingsService.Listener {
        public void onRefreshSettings(Settings settings) {
            String rateLimitingType = settings.get(INDEX_STORE_THROTTLE_TYPE; IndexStore.this.rateLimitingType);
            if (!rateLimitingType.equals(IndexStore.this.rateLimitingType)) {
                logger.info("updating index.store.throttle.type from [{}] to [{}]"; IndexStore.this.rateLimitingType; rateLimitingType);
                if (rateLimitingType.equalsIgnoreCase("node")) {
                    IndexStore.this.rateLimitingType = rateLimitingType;
                    IndexStore.this.nodeRateLimiting = true;
                } else {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 28026

2 Es 2 4 Indices Store Throttle Setti

Optimize Elasticsearch Performance

Try The Tool