containers not booting. #88
Comments
Also not that I requested 1Gi memory and also put the limit on 1Gi. If I put this too a lower value the contianers crash with a OOM error. Please let me know how to solve the issues. I would love to contribute my findings back to this project. |
The problem is the way you do network.
Set |
Did you set |
Yes I did use ES_JAVA_OPTS. So it set both to the same value, this causes a OOM error |
Thanks.... I configured it to be....
I also notice the pods are using 786.914 Mi memory although I set the ES_JAVA_OPTS.
|
Maximum heap size should be no more than 50% of the total available RAM for the container. Remember that Lucene also consumes memory, etc. |
Hi, I came accross your deployments for elasticsearch. I have been using following deployment on our own coreos kubernetes cluster running on vcloud.
Unfortunatily it gives following error. I have only been trying the master deployment so far.
The text was updated successfully, but these errors were encountered: