MaxContentLength set to high value; resetting it to 100mb – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

Briefly, this error message indicates that the maximum content length for a request is set to a high value. The maximum content length controls the size of requests that can be processed by Elasticsearch. To resolve the issue, the maximum content length should be set to an appropriate value.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” MaxContentLength set to high value; resetting it to 100mb ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest-high-level.

Log Context

Log “MaxContentLength[{}] set to high value; resetting it to [100mb]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         this.pipeliningMaxEvents = SETTING_PIPELINING_MAX_EVENTS.get(settings);
        this.corsConfig = buildCorsConfig(settings);

        // validate max content length
        if (maxContentLength.getBytes() > Integer.MAX_VALUE) {
            logger.warn("maxContentLength[{}] set to high value; resetting it to [100mb]"; maxContentLength);
                    "out of bounds max content length value [{}] will no longer be truncated to [100mb]; you must enter a valid setting";
            maxContentLength = new ByteSizeValue(100; ByteSizeUnit.MB);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content