# CheckIndex for shared gateway copy? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 13, 2013, 9:39pm UTC](https://discuss.elastic.co/t/checkindex-for-shared-gateway-copy/10731 "2013-02-13T21:39:10Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Paul\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_smith/32/1323_2.png) [@Paul\_Smith](https://discuss.elastic.co/u/Paul_Smith)\ **Post date:** [February 13, 2013, 9:39pm UTC](https://discuss.elastic.co/t/checkindex-for-shared-gateway-copy/10731/1 "2013-02-13T21:39:10Z")
Hi All, 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? regards, Paul Smith -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:51am UTC](https://discuss.elastic.co/t/checkindex-for-shared-gateway-copy/10731/2 "2017-07-06T02:51:32Z")
Closed on July 6, 2017, 2:51am UTC