Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes necessary for XL to work with Elasticsearch 8. Main change is that ES 8 has security (and TLS) enabled by default, so we now have to user+pass over HTTPS when talking to the ES cluster (certificate generation and stuff like that is handled automatically by ES when starting for the first time).
The devops part has already been merged.
How to tune things for search speed is a separate issue that we can look at more once we have QA running in the new ES cluster. The increased
number_of_shards
/number_of_replicas
is just a starting point based on our current usage in the main cluster and current recommendations (and anyway we should makenumber_of_shards
andnumber_of_replicas
configurable, but that's a devops thing).