Briefly, this error occurs when Elasticsearch takes longer than expected to send a transport message due to its large size. This could be due to network latency, insufficient resources, or inefficient queries. To resolve this, you can optimize your queries, increase your network bandwidth, or scale up your Elasticsearch cluster resources. Additionally, consider breaking down large data into smaller chunks to improve transport speed.
This guide will help you check for common problems that cause the log ” sending transport message [{}] of size [{}] on [{}] took [{}ms] which is above the warn ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “sending transport message [{}] of size [{}] on [{}] took [{}ms] which is above the warn ” classname is OutboundHandler.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
private void maybeLogSlowMessage(boolean success) {
final long logThreshold = slowLogThresholdMs;
if (logThreshold > 0) {
final long took = threadPool.relativeTimeInMillis() - startTime;
if (took > logThreshold) {
logger.warn("sending transport message [{}] of size [{}] on [{}] took [{}ms] which is above the warn " +
"threshold of [{}ms] with success [{}]"; message; messageSize; channel; took; logThreshold; success);
}
}
}
});
