Opster Team
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 size 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 size reached the maximum allowed of [” classname is ThreadContext.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
assert value != null; long newWarningHeaderSize = warningHeadersSize; //check if we can add another warning header - if max size within limits if (key.equals("Warning") && (maxWarningHeaderSize != -1)) { //if size is NOT unbounded; check its limits if (warningHeadersSize > maxWarningHeaderSize) { // if max size has already been reached before logger.warn("Dropping a warning header; as their total size reached the maximum allowed of [" + maxWarningHeaderSize + "] bytes set in [" + HttpTransportSettings.SETTING_HTTP_MAX_WARNING_HEADER_SIZE.getKey() + "]!"); return this; } newWarningHeaderSize += "Warning".getBytes(StandardCharsets.UTF_8).length + value.getBytes(StandardCharsets.UTF_8).length;
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Try FreeConnect in under 3 minutes
Arpit Ghiya
Senior Lead SRE at Coupa