Handling request took ms which is above the warn threshold of ms – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-7.15

Briefly, this error occurs when Elasticsearch takes more time to handle a request than the set warning threshold. This could be due to heavy indexing, slow queries, or insufficient resources. To resolve this, you can optimize your queries, increase your hardware resources, or adjust the warning threshold if it’s set too low. Also, consider using the Elasticsearch slow logs feature to identify slow queries and operations. Regular monitoring and maintenance of your Elasticsearch cluster can help prevent such issues.

This guide will help you check for common problems that cause the log ” handling request [{}][{}][{}][{}] took [{}ms] which is above the warn threshold of [{}ms] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: threshold, request.

Log Context

Log “handling request [{}][{}][{}][{}] took [{}ms] which is above the warn threshold of [{}ms]” classname is AbstractHttpServerTransport.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            handleIncomingRequest(httpRequest; httpChannel; httpRequest.getInboundException());
        } finally {
            final long took = threadPool.relativeTimeInMillis() - startTime;
            final long logThreshold = slowLogThresholdMs;
            if (logThreshold > 0 && took > logThreshold) {
                logger.warn("handling request [{}][{}][{}][{}] took [{}ms] which is above the warn threshold of [{}ms]";
                    httpRequest.header(Task.X_OPAQUE_ID); httpRequest.method(); httpRequest.uri(); httpChannel; took; logThreshold);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?