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

System requirements update elasticsearch/opensearch needed #432

Closed
chriz-uniba opened this issue Oct 31, 2022 · 3 comments · Fixed by #569
Closed

System requirements update elasticsearch/opensearch needed #432

chriz-uniba opened this issue Oct 31, 2022 · 3 comments · Fixed by #569

Comments

@chriz-uniba
Copy link
Contributor

The following lines need some update wrt. opensearch:

!!! note "Elasticsearch vs OpenSearch"
InvenioRDM will be transitioning from Elasticsearch to OpenSearch due to license changes in Elasticsearch which means it is no longer an open source product. We are currently assessing if it is feasible from a technical and resource perspective to support both products.

@chriz-uniba
Copy link
Contributor Author

Also here:

#### Elasticsearch and Docker (macOS and Linux)
Among the containers you will run is an Elasticsearch container which is quite demanding.
Per Elasticsearch's [Docker documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/docker.html#docker-prod-prerequisites),
you will want to apply the following kernel setting:
On Linux, add the following to ``/etc/sysctl.conf`` on your local machine (host machine):
```bash
# Maximum number of memory map areas a process (Elasticsearch) may have
vm.max_map_count=262144
```
On macOS, do the following:
```bash
screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
# and in the shell
sysctl -w vm.max_map_count=262144
```

@psaiz
Copy link
Contributor

psaiz commented Jun 26, 2023

I have the feeling that this was addressed in #551
@kpsherva, would you mind confirming it?

@psaiz psaiz self-assigned this Jun 29, 2023
@psaiz
Copy link
Contributor

psaiz commented Jun 29, 2023

So, the first comment was indeed already addressed. The second one, about the requirements is not. Thanks for pointing this out!
I'll send a new PR to address it

@psaiz psaiz removed their assignment Jun 29, 2023
@psaiz psaiz removed their assignment Jun 30, 2023
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 a pull request may close this issue.

2 participants