[jboss-jira] [JBoss JIRA] (SWSQE-294) Investigate ElasticSearch memory requirements on B24 cluster

Pavol Loffay (JIRA) issues at jboss.org
Mon Jul 16 11:13:00 EDT 2018


    [ https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605663#comment-13605663 ] 

Pavol Loffay commented on SWSQE-294:
------------------------------------

This definitely a problem related to resources. 512 is indeed is not enough for production deployments. 

The issue can be also related to lucene issues in ES 5.2.2 (the version we are using) https://discuss.elastic.co/t/elasticsearch-5-2-2-out-of-memory-while-indexing/78457/2. 

> Investigate ElasticSearch memory requirements on B24 cluster
> ------------------------------------------------------------
>
>                 Key: SWSQE-294
>                 URL: https://issues.jboss.org/browse/SWSQE-294
>             Project: Kiali QE
>          Issue Type: Bug
>            Reporter: Kevin Earls
>            Assignee: Guilherme Baufaker Rêgo
>            Priority: Minor
>         Attachments: elasticsearch-0.log, elasticsearch-pod-description.log, es1.log
>
>
> On minishift and the CNCF CI OpenShift cluster, we install ElasticSearch using the commands:
>     curl https://raw.githubusercontent.com/RHsyseng/docker-rhel-elasticsearch/5.x/es-cluster-deployment.yml --output es-cluster-deployment.yml
>     oc create -f es-cluster-deployment.yml
> However, on B24 this fails.  The first 2 elasticsearch pods will start up, but then elasticsearch-2 gets into the following failure loop like:
> elasticsearch-2   1/1       Running   3         1m
> elasticsearch-2   0/1       OOMKilled   3         1m
> elasticsearch-2   0/1       CrashLoopBackOff   3         2m
> If I increase memory in the es-cluster-deployment.yml to 1Gi it will at least start, but I've found I really need to increase it to 2Gi to do anything non trivial.  
> We may need to track down the people who originally created this template for help on this. 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)



More information about the jboss-jira mailing list