-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Fix index creation and rebuild #2265
Comments
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 ^^) |
@azgaviperr Hello, what is your issue ? |
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 |
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,
|
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
)The text was updated successfully, but these errors were encountered: