Log MaxContentLength set to high value; resetting it to 100mb – How To Solve Related Issues



Log 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 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 ” MaxContentLength set to high value; resetting it to 100mb ” 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: rest-high-level.

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 “MaxContentLength[{}] set to high value; resetting it to [100mb]” classname is Netty4HttpServerTransport.java
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);
            deprecationLogger.deprecated(
                    "out of bounds max content length value [{}] will no longer be truncated to [100mb]; you must enter a valid setting";
                    maxContentLength.getStringRep());
            maxContentLength = new ByteSizeValue(100; ByteSizeUnit.MB);
        }






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 11244

2 Github Issue Number 2237






Optimize Elasticsearch Performance

Try The Tool