[JBoss JIRA] (ISPN-8478) Reduce build memory usage
by Dan Berindei (JIRA)
Dan Berindei created ISPN-8478:
----------------------------------
Summary: Reduce build memory usage
Key: ISPN-8478
URL: https://issues.jboss.org/browse/ISPN-8478
Project: Infinispan
Issue Type: Task
Components: Build process
Affects Versions: 9.2.0.Alpha2
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 9.2.0.Beta1
The CI Maven process runs without a max heap parameter, so it can use up to 1/4 of agent RAM. It should run with a specific limit and so should all the other JVMs it spawns: the surefire fork, Karaf containers, WildFly servers etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (ISPN-8452) KUBE_PING doesn't work with JDG 7.2 OpenShift image
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-8452?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-8452:
-------------------------------
Priority: Blocker (was: Major)
> KUBE_PING doesn't work with JDG 7.2 OpenShift image
> ---------------------------------------------------
>
> Key: ISPN-8452
> URL: https://issues.jboss.org/browse/ISPN-8452
> Project: Infinispan
> Issue Type: Bug
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Priority: Blocker
>
> It seems that KUBE_PING doesn't work with the latest version of JDG 7.2 OpenShift image. The reason for this is that JDG 7.2 is shipped with upstream KUBE_PING which conflicts with the one provided in the openshift layer.
> The easiest solution is to revert layer ordering {{layers.conf}} file:
> {code}
> echo "layers=base,openshift" > /opt/datagrid/modules/layers.conf
> {code}
> This solution has additional advantage - we can fallback to previous KUBE_PING version (the one provided by the CE Team) by just changing this small line.
> However if the upstream KUBE_PING works fine and we are happy with it, we should remove the old version from the server. I think that's a solution we should take for JDG 8 or maybe sooner - 7.3.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months