# Was CRC32 in version 7.x of Elasticsearch?
**URL:** https://discuss.elastic.co/t/was-crc32-in-version-7-x-of-elasticsearch/352558
**Category:** Elasticsearch
**Created:** [February 5, 2024, 5:21pm UTC](https://discuss.elastic.co/t/was-crc32-in-version-7-x-of-elasticsearch/352558 "2024-02-05T17:21:58Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ncluff](https://discuss.elastic.co/u/ncluff)
#### Post date: [February 5, 2024, 5:21pm UTC](https://discuss.elastic.co/t/was-crc32-in-version-7-x-of-elasticsearch/352558/1 "2024-02-05T17:21:58Z")
I noticed [this post](https://discuss.elastic.co/t/checksum-failed-hardware-problem/341061/2) where David Turner mentions the troubleshooting guide for corruption. The documentation started in 8.3, but I'm curious if this is the same for version 7.17.4?
Backstory, I have a deployment on VMWare Vsphere with VSAN backing and I have other Elasticsearch deployments on it, but only one VM is having the `org.apache.lucene.index.CorruptIndexException` error coming up frequently and I'm not sure why. This VM is has ES hosted in K8s, and I'm not sure if that makes a difference.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [February 5, 2024, 5:58pm UTC](https://discuss.elastic.co/t/was-crc32-in-version-7-x-of-elasticsearch/352558/2 "2024-02-05T17:58:33Z")
> [@ncluff](#):
>
> I'm curious if this is the same for version 7.17.4?
Yep, same in that version, this was added [about a decade ago](https://github.com/elastic/elasticsearch/issues/5924). Indeed I'm not sure there's ever been an explanation for this sort of exception that isn't environmental.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 4, 2024, 5:59pm UTC](https://discuss.elastic.co/t/was-crc32-in-version-7-x-of-elasticsearch/352558/3 "2024-03-04T17:59:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.