Firstly, I know the Shared Gateway is now deprecated, but...
I also know ES has a configuration item to start the cluster in a mode to
run Lucene's CheckIndex feature which is awesome. Additionally just
running the CheckIndex main class from the Lucene jar shipped with ES and
pointing it to the shard directories does the same thing, so one can verify
a node's shard indices.
However the shared gateway file structure is different, the 'segment' files
in there look to be a combined form of the lucene structure.
I was hoping to be able to verify via the CheckIndex tool whether the
tertiary copy of our shared gateway is not corrupted, but it doesn't seem
possible ? Any ideas?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.