Log Message read past expected size (request) for requestId=. action . readerIndex vs expected . resetting – How To Solve Related Issues

Log Message read past expected size (request) for requestId=. action . readerIndex vs expected . resetting – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Message read past expected size (request) for requestId=. action . readerIndex vs expected . resetting” it’s important to understand a few problems related to Elasticsearch concepts handler, index, netty, request. See bellow important tips and explanations on these concepts

Log Context

Log”Message read past expected size (request) for requestId=[{}]; action [{}]; readerIndex [{}] vs expected [{}]; resetting” classname is MessageChannelHandler.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (buffer.readerIndex() != expectedIndexReader) {
                if (buffer.readerIndex() 



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Java Io Streamcorruptedexception Af  

Github Issue Number 17090  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now