receive_timeout_transport_exception: Request timed out waiting for a response from another node
ElasticsearchWhat does it mean?
A node sent a request to another node, but the response did not arrive within the configured time and the request timed out. The inter-node (transport) call could not complete.
Why does it happen?
The target node under heavy load, long GC pauses, slow disk/CPU pressure, network latency/packet loss, or the target node being too busy to respond. Common during heavy queries, large bulk operations and shard rebalancing.
How to fix it
Inspect resource usage on the affected nodes: check JVM heap, GC and thread pool saturation with GET _nodes/stats. Check rejected/queued tasks with GET _cat/thread_pool?v. Measure network latency. Reduce the load (smaller query/bulk sizes) and review heap and hardware resources. If persistent, add nodes to distribute the load.
More from this engine
- not_x_content_exceptionCompressor detection error / body is not valid content
- document_source_missing_exceptionDocument source is missing
- node_not_connected_exceptionNode is not connected
- routing_missing_exceptionRouting value is required for this document
- too_many_buckets_exceptionTrying to create too many buckets
- shard_lock_obtain_failed_exceptionObtaining shard lock timed out
- parsing_exceptionFailed to parse the search request / query DSL