[
https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin....
]
Kevin Earls commented on SWSQE-294:
-----------------------------------
Bonjour,
En l'absence de votre correspondant, merci d'adresser votre email à Michael Foley
- mfoley(a)redhat.com.
Bien cordialement.
-
Dear Sender,
In the absence of your contact, please send your email to Michael Foley -
mfoley(a)redhat.com.
Many thanks.
-
Lieber Absender,
In Abwesenheit Ihrers Kontaktes senden Sie Ihre E-Mail bitte an Michael Foley -
mfoley(a)redhat.com.
Vielen Dank.
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: 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/...
--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)