Dropping a warning header; as their total count reached the maximum allowed of – How to solve related issues

Average Read Time

2 Mins

Dropping a warning header; as their total count reached the maximum allowed of – 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 ” Dropping a warning header; as their total count reached the maximum allowed of ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: thread.

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 “Dropping a warning header; as their total count reached the maximum allowed of [” classname is ThreadContext.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
            //check if we can add another warning header - if max count within limits
            if ((key.equals("Warning")) && (maxWarningHeaderCount != -1)) { //if count is NOT unbounded; check its limits
                final int warningHeaderCount = newResponseHeaders.containsKey("Warning") ? newResponseHeaders.get("Warning").size() : 0;
                if (warningHeaderCount > maxWarningHeaderCount) {
                    logger.warn("Dropping a warning header; as their total count reached the maximum allowed of ["
                            + maxWarningHeaderCount + "] set in ["
                            + HttpTransportSettings.SETTING_HTTP_MAX_WARNING_HEADER_COUNT.getKey() + "]!");
                    return this;
                }
            }




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content