Does Elasticsearch have any history of not being compatible with Vormetric?

Elastic Search
1

Quick question: Does Elasticsearch have any history of not being compatible with Vormetric?

A have a user of our system who is using Vormetric (I think to do transparent file system level encryption) who is encountering the checksum failed (hardware problem?) error which I've read is due to corrupting the data after Elasticsearch has written it out. I don't dispute that this isn't an Elasticsearch issue, but I was hoping that someone could take a quick look at any internal issue tracking system to see if this is a known issue with Vormetric.

Thanks!

[2024-05-30T00:53:47,563][WARN ][org.elasticsearch.index.engine.Engine] [wpaapn250153090.cbsh.com] [<>][0] failed engine [merge failed]
org.apache.lucene.index.MergePolicy$MergeException: org.apache.lucene.index.CorruptIndexException: checksum failed (hardware problem?) : expected=7adabfaa actual=699e3c1 (resource=BufferedChecksumIndexInput(NIOFSIndexInput(path="<>")))
2

This is a community forum so I am not sure there are many people that have experience of using Vormetric together with Elasticsearch. I did not see anything around Vormetric in the Elasticsearch repo either.

Elastic Support may have more information, but I am not sure to what extent they hang out here or would be willing to share that information.

As Vormetric affects the file system it sounds like it likely could be causing the issue, especially if none of your other customers that do not use Vormetric have the same issue.

You did not mention which version of Elasticsearch you are using, but a lot of resiliency i.provements have been done in the last few version which I believe make Elasticsearch more likely to detect file system issues.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.