[Bug] Fix index creation and rebuild

[To-om]

Request Type

Bug

Problem Description

The index creation is not correctly rebuilt after a database restore. Only one index should be used (managed by Elasticsearch or Lucene). All composite indices should be removed. When the index is not available, TheHive should refuse to start (db.janusgraph.dropAndRebuildIndexOnFailure: false) or remove the index and rebuild a new one (db.janusgraph.dropAndRebuildIndexOnFailure: true)

[azgaviperr]

Hello, where should be set db.janusgraph.dropAndRebuildIndexOnFailure: true ?

I added it to the application.conf.

Got currently an index issue after ugrading to 3.15.1 (forgot to change :latest ^^)

[To-om]

@azgaviperr Hello, what is your issue ?

[azgaviperr]

I fixed my issue with the index from the upgrade (container was restarting before finishing reindex).

However I am not sure where to setup db.janusgraph.dropAndRebuildIndexOnFailure: true

[To-om]

this settings should not be set to true in normal use, otherwise TheHive will remove index and rebuild it if the index engine is not ready yet at startup (can occur when using docker-compose for example). If should be set to true if you known that the index need to be rebuilt.

To answer you question, db.janusgraph.dropAndRebuildIndexOnFailure is the full path of the config. You can set it in root section in application.conf. Or you can set dropAndRebuildIndexOnFailure under db.janusgraph section:

db.janusgraph {
  storage {
    backend: cql
    // [...]
  }
  index.search {
    backend: lucene
    // [...]
  }

  dropAndRebuildIndexOnFailure: false
}
    

[azgaviperr]

Happy I did pretty much understand this ^^

Thanks for the info.