[jboss-jira] [JBoss JIRA] (SWSQE-118) ElasticSearch deployment fails on B11 cluster with out of memory errors

Guilherme Baufaker Rêgo (JIRA) issues at jboss.org
Thu Apr 5 08:04:00 EDT 2018


     [ https://issues.jboss.org/browse/SWSQE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guilherme Baufaker Rêgo reassigned SWSQE-118:
---------------------------------------------

    Assignee: Guilherme Baufaker Rêgo  (was: Michael Foley)


> ElasticSearch deployment fails on B11 cluster with out of memory errors
> -----------------------------------------------------------------------
>
>                 Key: SWSQE-118
>                 URL: https://issues.jboss.org/browse/SWSQE-118
>             Project: Kiali QE
>          Issue Type: QE Task
>            Reporter: Kevin Earls
>            Assignee: Guilherme Baufaker Rêgo
>            Priority: Blocker
>
> As part of KIALI-336 I'm trying to run Jaeger with ElasticSearch as its storage, using this Jenkinsfile:  https://github.com/jaegertracing/jaeger-performance/blob/master/standalone/Jenkinsfile
> The test is setup on B11 in the jaeger-test project https://jenkins-jaeger-test.openshift4.jonqe.lab.eng.bos.redhat.com/job/Jaeger%20Standalone%20Performance%20Tests/
> I'm running into a few problems here, which may or may not be related.
> 1.  Even though I've run this test twice, Jenkins does not have any logs.
> 2.  ElasticSearch will not start up.  I don't have the exact log of the problem yet, as it keeps trying to redeploy, but I have seen "Oom" errors messages, which I assume means out of memory.  I will attach logs if I can catch it in this exact state.



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



More information about the jboss-jira mailing list