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 can resolve issues that cause many errors.

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.

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 “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

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content