ElasticSearch: Difference between revisions
No edit summary |
No edit summary |
||
Line 27: | Line 27: | ||
</pre> | </pre> | ||
== Creds havers == | |||
* [[Jonny]] | |||
* [[Lina]] | |||
== References == | == References == | ||
Line 47: | Line 48: | ||
* [[Search]] | * [[Search]] | ||
== Discord == | |||
== History == | |||
=== Threads === | |||
* Initial enabling with [[Jonny]] and [[Lina]] - https://discord.com/channels/1049136631065628772/1052452072806686751/1167287930742652958 | |||
=== Discord === | |||
{{Message | {{Message |
Revision as of 03:16, 27 October 2023
Config
List any changed config values here!!!
/etc/elasticsearch/elasticsearch.yml
:
network.host: localhost discovery.type: single-node xpack.security.enabled: true
/home/mastodon/.env.production
idk if we should put this part online but there is some config here too
Memory
the ES docs say to allocate half your available memory to the heap. At the moment (23-10-26) we are using 2.5G/8G memory at rest. Going to try allocating 3GB and see what happens
/etc/elasticsearch/jvm.options.d/heap.options
-Xms3g -Xmx3g
Creds havers
References
Docs:
- https://docs.joinmastodon.org/admin/elasticsearch/
- THIS is actually the current docs, the other urls that are EXACTLY THE SAME are no longer maintained - https://www.elastic.co/guide/en/elasticsearch/reference/current/advanced-configuration.html#set-jvm-heap-size
- https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html
- https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html
- https://blog.thms.uk/2023/09/mastodon-elasticsearch
- (pretty old at this point and also ES says not do to the JVM memory size thing) https://github.com/felx/mastodon-documentation/blob/master/Running-Mastodon/Elasticsearch-guide.md
Since we are running on a small VPS, we might need to configure it for a low memory environment!
See also
History
Threads
- Initial enabling with Jonny and Lina - https://discord.com/channels/1049136631065628772/1052452072806686751/1167287930742652958
Discord
OK yet again starting thread on getting ElasticSearch running