Log Indices.store.throttle.max_bytes_per_sec – How To Solve Related Issues


Log Indices.store.throttle.max_bytes_per_sec – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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 ” Updating indices.store.throttle.max-bytes-per-sec from to ; note; type is ” 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: indices.

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 (free tool that requires no installation).

Log context

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

                 IndicesStore.this.rateLimiting.setType(rateLimitingType);
            }

            ByteSizeValue rateLimitingThrottle = settings.getAsBytesSize(INDICES_STORE_THROTTLE_MAX_BYTES_PER_SEC; IndicesStore.this.rateLimitingThrottle);
            if (!rateLimitingThrottle.equals(IndicesStore.this.rateLimitingThrottle)) {
                logger.info("updating indices.store.throttle.max_bytes_per_sec from [{}] to [{}]; note; type is [{}]"; IndicesStore.this.rateLimitingThrottle; rateLimitingThrottle; IndicesStore.this.rateLimitingType);
                IndicesStore.this.rateLimitingThrottle = rateLimitingThrottle;
                IndicesStore.this.rateLimiting.setMaxRate(rateLimitingThrottle);
            }
        }
    }




 

Optimize Elasticsearch Performance

Try The Tool