hochschule-darmstadt / openartbrowser

Exploring the world of arts using open data
http://openartbrowser.org/
MIT License
40 stars 10 forks source link

Update Elasticsearch version on staging/prod and fix ram usage #539

Closed DavidReyer closed 3 years ago

DavidReyer commented 3 years ago

Reason (Why?) The Elasticsearch versions on the staging and production server are currently mismatched and outdated. Staging currently runs on version 7.12 and production on 7.0. The current version is 7.13.

Additionally the current staging elasticsarch configuration uses half of the available ram as heap, currently 16GB. This is a bit excessive and it should be adjusted to better fit the needs of the server. The production server on the other hand only is limited to using only 1GB which is probably not enough.

Solution (What?) Update both versions of the elasticsearch. Check how much ram should be sufficient for running the elasticsearch service smoothly and adjust both servers accordingly.

Acceptance criteria Both servers are on the same version, with the same configuration and running smoothly.

DavidReyer commented 3 years ago

The upgrade is done. Both the staging and the production server are now running on ES version 7.13.2. The upgrade was done following this guide.

Additionally the ES ram usage was limited on both servers, following this guide. The servers now use at a minimum 4GB and at a maximum 8GB of ram.

This has been documented here and the Elasticsearch section of the installation guide has been updated.