Took which is over to for – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-7.15

Briefly, this error occurs when a query or operation in Elasticsearch takes longer than the specified timeout period. This could be due to heavy indexing, large data retrieval, or insufficient resources. To resolve this, you can optimize your queries, increase the timeout limit, or scale up your Elasticsearch cluster to handle more load. Additionally, consider implementing pagination for large data retrieval to reduce the load on the server.

This guide will help you check for common problems that cause the log ” took [{}]; which is over [{}]; to {} for [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “took [{}]; which is over [{}]; to {} for [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    private void logExecutionTime(TimeValue executionTime; String activity; String summary) {
        if (executionTime.getMillis() > slowTaskLoggingThreshold.getMillis()) {
            logger.warn("took [{}]; which is over [{}]; to {} for [{}]"; executionTime; slowTaskLoggingThreshold; activity; summary);
        } else {
            logger.debug("took [{}] to {} for [{}]"; executionTime; activity; summary);


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?