In one our environment we are facing the "CorruptIndexException". While analyzing the elastic log we found the below are the list of exception details: infinity_infinity-elasticsearch.1.862455ajz1ca@WorkerNode03Prod | {"type": "server", "timestamp": "2023-06-30T11:18:47,132Z", "level": "INFO", …

Facing java.io.EOFException: read past EOF exception and org.apache.lucene.index.CorruptIndexException: compound sub-files must have a valid codec header and footer: file is too small (0 bytes) in elastic 7.17.5

Christian_Dahlqvist (Christian Dahlqvist) July 14, 2023, 5:38am 2

Failure to downloadthe geoip file is unlrelated to the corruption issue. I suspect that your issue is related to the type of storage you are using. See this recent thread for more details.

Topic		Replies	Views
"stacktrace": ["org.apache.lucene.index.CorruptIndexException: compound sub-files must have a valid codec header and footer: file is too small (0 bytes) (resource=BufferedChecksumIndexInput) Elasticsearch	22	808	August 25, 2023
Compound sub-files must have a valid codec header and footer: file is too small (0 bytes) Elasticsearch	3	1216	September 11, 2019
["org.elasticsearch.bootstrap.StartupException: ElasticsearchException[failed to bind service]; nested: CorruptIndexException[codec footer mismatch (file truncated?) Elasticsearch	12	853	December 21, 2023
["org.apache.lucene.index.CorruptIndexException: checksum failed (hardware problem?) Elasticsearch docker , language-clients	1	197	March 18, 2024
Likely root cause: org.elasticsearch.gateway.CorruptStateException: codec footer mismatch (file truncated?): actual footer=-993495054 vs expected footer=-1071082520 Elasticsearch	8	3860	August 23, 2019

Facing java.io.EOFException: read past EOF exception and org.apache.lucene.index.CorruptIndexException: compound sub-files must have a valid codec header and footer: file is too small (0 bytes) in elastic 7.17.5

Related Topics