Received response for a request that has timed out; sent ms ago; timed out ms ago; – How to solve related issues

Average Read Time

2 Mins

Received response for a request that has timed out; sent ms ago; timed out ms ago; – 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 ” Received response for a request that has timed out; sent ms ago; timed out ms ago; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request and response.

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 “Received response for a request that has timed out; sent [{}ms] ago; timed out [{}ms] ago;” classname is TransportService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         final String action;
        assert responseHandlers.contains(requestId) == false;
        TimeoutInfoHolder timeoutInfoHolder = timeoutInfoHandlers.remove(requestId);
        if (timeoutInfoHolder != null) {
            long time = threadPool.relativeTimeInMillis();
            logger.warn("Received response for a request that has timed out; sent [{}ms] ago; timed out [{}ms] ago; " +
                    "action [{}]; node [{}]; id [{}]"; time - timeoutInfoHolder.sentTime(); time - timeoutInfoHolder.timeoutTime();
                timeoutInfoHolder.action(); timeoutInfoHolder.node(); requestId);
            action = timeoutInfoHolder.action();
            sourceNode = timeoutInfoHolder.node();
        } else {




 

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

Analyze your cluster

Skip to content