Log MaxContentLength – How To Solve Related Issues


Log MaxContentLength – 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 ” MaxContentLength ” 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: netty.

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 “maxContentLength[” classname is NettyHttpServerTransport.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         this.pipeliningMaxEvents = settings.getAsInt(SETTING_PIPELINING_MAX_EVENTS; DEFAULT_SETTING_PIPELINING_MAX_EVENTS);
        this.corsConfig = buildCorsConfig(settings);

        // validate max content length
        if (maxContentLength.bytes() > Integer.MAX_VALUE) {
            logger.warn("maxContentLength[" + maxContentLength + "] set to high value; resetting it to [100mb]");
            maxContentLength = new ByteSizeValue(100; ByteSizeUnit.MB);
        }
        this.maxContentLength = maxContentLength;

        logger.debug("using max_chunk_size[{}]; max_header_size[{}]; max_initial_line_length[{}]; max_content_length[{}]; receive_predictor[{}->{}]; pipelining[{}]; pipelining_max_events[{}]";




 





Optimize Elasticsearch Performance

Try The Tool