Backend and orborus connection issues

[Farru19]

Backend and orborus connection issues

[frikky]

Hey! Based on the Opensearch logs, it is failing to allocate memory for your server.

[2024-02-28T10:36:25,170][WARN ][o.o.b.JNANatives         ] [shuffle-opensearch] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory
[2024-02-28T10:36:25,172][WARN ][o.o.b.JNANatives         ] [shuffle-opensearch] This can result in part of the JVM being swapped out.
[2024-02-28T10:36:25,172][WARN ][o.o.b.JNANatives         ] [shuffle-opensearch] Increase RLIMIT_MEMLOCK, soft limit: 8388608, hard limit: 8388608
[2024-02-28T10:36:25,172][WARN ][o.o.b.JNANatives         ] [shuffle-opensearch] These can be adjusted by modifying /etc/security/limits.conf, for example: 

99% of the time we have problems, it's Opensearch. What were the problems you had with the memlock limits in place? These are required, otherwise they wouldn't be there.

[Farru19]

When I ran docker compose without commenting memlock limits, it would keep running in loop until I had to stop using ctrl + c. Only to see all other containers runnning expect opensearch was not installed. Anyways I shifted from lxc containers and created a standlone VM with 2 cores and 8Gs of memory. Everything runs fine now! Problems only occured when using LXC Containers.