Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Message not fully read (request) for and action . resetting ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: handler and netty.
Log Context
Log “Message not fully read (request) for [{}] and action [{}]; resetting” classname is MessageChannelHandler.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (TransportStatus.isRequest(status)) {
String action = handleRequest(ctx.getChannel(); wrappedStream; requestId; version);
if (buffer.readerIndex() != expectedIndexReader) {
if (buffer.readerIndex()
Find & fix Elasticsearch problems
