aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/portal/components/portal-cassandra/values.yaml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2021-02-15 15:28:19 +0100
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2021-02-16 07:04:22 +0000
commitc23aa42a3c3f7c864544be41837f8601d264f1a5 (patch)
tree1dc9a60e1e9837d6a8bb08c08c00a1aeaefa342c /kubernetes/portal/components/portal-cassandra/values.yaml
parent8d99c0d80b9335eab7d20bb074d0b007358ce013 (diff)
[PORTAL] Fix Heap config generation
When tried to apply heap configuration for small flavors, weird side effects have appeared. This patch solves them by doing a more generic way of configuring heap variables for cassandra. Issue-ID: PORTAL-1037 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Iebe2edd5281213580d9e1d4d86f9ca0b2abd2601
Diffstat (limited to 'kubernetes/portal/components/portal-cassandra/values.yaml')
-rw-r--r--kubernetes/portal/components/portal-cassandra/values.yaml20
1 files changed, 12 insertions, 8 deletions
diff --git a/kubernetes/portal/components/portal-cassandra/values.yaml b/kubernetes/portal/components/portal-cassandra/values.yaml
index c185155f09..b06761a870 100644
--- a/kubernetes/portal/components/portal-cassandra/values.yaml
+++ b/kubernetes/portal/components/portal-cassandra/values.yaml
@@ -112,14 +112,6 @@ flavor: small
# Segregation for Different environment (Small and Large)
resources:
small:
- # Heap size is tightly correlated to RAM limits.
- # If limit > 8G, Cassandra should define itself the best value.
- # If not, you must set up it in a coherent way with limits set
- # Refer to https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/operations/opsTuneJVM.html#Determiningtheheapsize
- # for more informations.
- heap:
- max: 3G
- new: 100M
limits:
cpu: 500m
memory: 3.75Gi
@@ -134,3 +126,15 @@ resources:
cpu: 2
memory: 6Gi
unlimited: {}
+
+heap:
+ # Heap size is tightly correlated to RAM limits.
+ # If limit > 8G, Cassandra should define itself the best value.
+ # If not, you must set up it in a coherent way with limits set
+ # Refer to https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/operations/opsTuneJVM.html#Determiningtheheapsize
+ # for more informations.
+ small:
+ max: 3G
+ new: 100M
+ large: {}
+ unlimited: {} \ No newline at end of file