Elasticsearch pod in CrashLoopbackOff caused by CorruptIndexException in RHOCP 4

Solution Verified - Updated -

Issue

  • The Elasticsearch pod is in CrashLoopBackOff with the error:

    org.elasticsearch.bootstrap.StartupException: ElasticsearchException[java.io.IOException: failed to read [id:186, file:/elasticsearch/persistent/elasticsearch/data/nodes/0/_state/node-186.st]]; nested: IOException[failed to read [id:186, file:/elasticsearch/persistent/elasticsearch/data/nodes/0/_state/node-186.st]]; nested: CorruptStateException[org.apache.lucene.index.CorruptIndexException: codec footer mismatch (file truncated?): actual footer=1869639785 vs expected footer=-1071082520 (resource=BufferedChecksumIndexInput(SimpleFSIndexInput(path="/elasticsearch/persistent/elasticsearch/data/nodes/0/_state/node-186.st")))]; nested: CorruptIndexException[codec footer mismatch (file truncated?): actual footer=1869639785 vs expected footer=-1071082520 (resource=BufferedChecksumIndexInput(SimpleFSIndexInput(path="/elasticsearch/persistent/elasticsearch/data/nodes/0/_state/node-186.st")))];
    

Environment

  • Red Hat Openshift Container Platform (RHOCP)
    • 3
    • 4
  • Red Hat OpenShift Logging (RHOL)
    • 5
  • Elasticsearch

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content