Skip to content
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

Use Elasticsearch 8 #1309

Merged
merged 6 commits into from
Sep 18, 2023
Merged

Use Elasticsearch 8 #1309

merged 6 commits into from
Sep 18, 2023

Conversation

andersju
Copy link
Member

@andersju andersju commented Sep 15, 2023

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 make number_of_shards and number_of_replicas configurable, but that's a devops thing).

Copy link
Contributor

@olovy olovy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@olovy olovy merged commit 63f7a20 into develop Sep 18, 2023
1 check passed
@olovy olovy deleted the feature/lxl-3986-use-elasticsearch-8 branch September 18, 2023 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants