As the SDNC pod JVM limits are set to max 6Gi, the pod limits need to
be increased as well, otherwise the pod gets OOMKilled.
Instead of using fixed memory limits, now the maxRAMPercentage is defined.
Issue-ID: OOM-3332
Change-Id: I90245f5c1c5501be5e7a7deca9a722d70a82a267
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
- name: JAVA_HOME
value: "{{ .Values.config.javaHome}}"
- name: JAVA_OPTS
- value: "-Xms{{.Values.config.odl.javaOptions.minMemory}} -Xmx{{.Values.config.odl.javaOptions.maxMemory}}"
+ value: "-XX:MaxRAMPercentage={{.Values.config.odl.javaOptions.maxRAMPercentage}}"
- name: LOG4J_FORMAT_MSG_NO_LOOKUPS
value: "true"
- name: KARAF_CONSOLE_LOG_LEVEL
maxGCPauseMillis: 100
parallelGCThreads : 3
numberGCLogFiles: 10
- minMemory: 1028m
- maxMemory: 6144m
+ maxRAMPercentage: 70
gcLogOptions: ""
# Next line enables gc logging
# gcLogOptions: "-Xlog:gc=trace:file={{.Values.config.odl.gcLogDir}}/gc-%t.log}:time,level,tags:filecount={{.Values.config.odl.javaOptions.numberGCLogFiles}}"
small:
limits:
cpu: "2"
- memory: "4.7Gi"
+ memory: "7Gi"
requests:
cpu: "1"
- memory: "4.7Gi"
+ memory: "7Gi"
large:
limits:
cpu: "4"
- memory: "9.4Gi"
+ memory: "10Gi"
requests:
cpu: "2"
- memory: "9.4Gi"
+ memory: "10Gi"
unlimited: {}
#Pods Service Account