How To Solve Issues Related to Log – Received response for a request that has timed out; sent ms ago; timed out ms ago;

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) :
Troubleshooting Background       
Related Issues  
Log Context
About Opster

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 “Received response for a request that has timed out; sent ms ago; timed out ms ago;” it’s important to understand common problems related to Elasticsearch concepts: request, response. 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 Github Issue Number 36822  

2 Warn O E T Transportservice Esm3 Re  


Log Context

Log ”Received response for a request that has timed out; sent [{}ms] ago; timed out [{}ms] ago;” classname is TransportService.java
We have extracted the following from Elasticsearch source code to get 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 {






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

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

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?