I got this error when i tried to install elasticse...
# getting-started
g
I got this error when i tried to install elasticsearch by kubernetes . I setup my server with configuration of 8 GB RAM. Could it be out of memory. How can i fix it ? I am using your configuration on minikube
m
@early-lamp-41924 might have some ideas.
e
Hey! What's the error code you see on the top side of this kubectl describe pod?
g
Do you mean this ?
the rest of pods are okay but elastichseach
e
Looks like they are dying due to OOM. Since they are being OOM killed
What’s the cluster setup? (CPU and RAM) and are there other systems running in the cluster?
g
cluster setup has 4 CPUs and 8 GB RAM. And no other systems else are running
e
We've seen that the default config for elastic search uses a lot of resources. 3 Nodes with 2cpu and 8gb of ram were required 😢 You can try adjusting the resource limit for the elastic pod in the prerequisites-values.yaml !
g
When i tried to install components of datahub, it happened some components not be installed and gms component ran into error
i had checked the gms component. How can i fix it ?
m
For single server install : docker based install is the simplest. Is there a specific reason you have to use the k8s based deployment for single server?
e
Error 137 is out of memory. You are runnung out of resources. Probably bc elasticsearch is taking all the space.
g
Our System are running on Kubernetes. I want to test DataHub out before integrating into the system. Our server config is setup with 4 CPUs and 8GB RAM and it seems to be not enough. Is there any way i can run elasticsearch with one node instead of 3 nodes right now or 3 nodes are compulsory and it's not going to be changed ? If it's so, can you recommand for me the rational config for my sever that can gets rid off the out of memory error, please ?
e
In the prerequisites-value.yaml there are configurations that I commented out. Those configs were designed for minikube (single node local kubernetes), so it should work for this case as well.
Can you try uncommenting and deploy? Configs under elasticsearch
g
@lemon-receptionist-90470