# Corrupted index

**URL:** <https://community.stardog.com/t/corrupted-index/2111>\
**Category:** Support\
**Created:** [November 21, 2019, 7:52am UTC](https://community.stardog.com/t/corrupted-index/2111 "2019-11-21T07:52:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![FelipeQuirce](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/felipequirce/32/574_2.png) [@FelipeQuirce](https://community.stardog.com/u/FelipeQuirce)\
**Post date:** [November 21, 2019, 7:52am UTC](https://community.stardog.com/t/corrupted-index/2111/1 "2019-11-21T07:52:08Z")

</div>

I'm having problems starting the cluster, I found this error during the node sync com.complexible.stardog.StardogException: Drop conflicts with other create operation.

Then I tried to repair the database and I found this error [WARN] 2019-11-21 07:41:25.732 [stardog-user-62] com.complexible.stardog.index.io.IndexIO - Index cannot be repaired, result was Index is not valid.  
Valid Indexes: []  
Invalid Indexes: [SPOC, POS, SPO, OSP, PSO, PSOC, OSPC, POSC]  
Repair Index: null  
Dictionary: Inconsistent  
Statistics: Valid  
The index cannot be repaired.

How can I fix this issue and make sure it doesn't happen again?

If I have to run cluster with one node, we will probably migrate to JENA and save money.

Thanks.  
PD. We have a cluster of 3 nodes in version 7.0.3 in GKC(google kubernetes cluster) and we do streaming updates on the data aprox(1000 writes a day).

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)\
**Post date:** [December 5, 2019, 7:52am UTC](https://community.stardog.com/t/corrupted-index/2111/2 "2019-12-05T07:52:09Z")

</div>

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