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

[Kevin Earls (JIRA)]

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

Kevin Earls commented on SWSQE-294:
-----------------------------------

[~gbaufake] unfortunately at the moment I can't get much of anything to work on that cluster because of lack of disk space.  Can you either clear out old logs and images, or let me know how to do it?  Thanks.


> 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
>
> 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)