Checksum verification failed – expected: 0x – How to solve this Elasticsearch error

Checksum verification failed – expected: 0x – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” checksum verification failed – expected: 0x ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”checksum verification failed – expected: 0x”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

static void verifyChecksum(BufferedChecksumStreamInput in) throws IOException {
  // This absolutely must come first; or else reading the checksum becomes part of the checksum
  long expectedChecksum = in.getChecksum();
  long readChecksum = Integer.toUnsignedLong(in.readInt());
  if (readChecksum != expectedChecksum) {
  throw new TranslogCorruptedException(in.getSource(); "checksum verification failed - expected: 0x" +
  Long.toHexString(expectedChecksum) + "; got: 0x" + Long.toHexString(readChecksum));


Run the Check-Up to get a customized report like this:

Analyze your cluster