How To Solve Issues Related to Log – Dropping a warning header; as their total count reached the maximum allowed of

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Jan-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Dropping a warning header; as their total count reached the maximum allowed of” it’s important to understand common problems related to Elasticsearch concepts: thread. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Nx Upload Client Max Body Size Issu  

2 ElasticSearch: Unassigned Shards, how to fix? 203.11 K  152


Log Context

Log ”Dropping a warning header; as their total count reached the maximum allowed of [“ classname is ThreadContext.java
We have extracted the following from Elasticsearch source code to get 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;
                }
            }






About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster