TransportService is closed stopped can t send request – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.5

Briefly, this error occurs when an attempt is made to send a request to Elasticsearch while the TransportService, responsible for node-to-node communication, is closed or stopped. This could be due to a node shutdown or network issues. To resolve this, ensure that the Elasticsearch cluster is running and all nodes are properly connected. If the issue persists, check the network connectivity and firewall settings. Restarting the Elasticsearch service or the entire node may also help. If the problem continues, consider checking the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” TransportService is closed stopped can’t send request ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request.

Log Context

Log “TransportService is closed stopped can’t send request” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * caller. It will only notify if toStop hasn't done the work yet.
 * Do not edit this exception message; it is currently relied upon in production code!
 // TODO: make a dedicated exception for a stopped transport service? cf. ExceptionsHelper#isTransportStoppedForAction
 throw new TransportException("TransportService is closed stopped can't send request");
 if (timeoutHandler != null) {
 assert options.timeout() != null;


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?