summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJan Wozniak <jwozniak@redhat.com>2017-07-14 10:17:42 +0200
committerJan Wozniak <jwozniak@redhat.com>2017-07-14 10:17:46 +0200
commit711ba660dcfca9bb3739a5e45c4bc9a5f1e75cc1 (patch)
treec1acc23aa798bbd57bd259d27577b620dddfb504
parent0b0a7af456c8786dace49bb38ecf462c8f3336c3 (diff)
downloadopenshift-711ba660dcfca9bb3739a5e45c4bc9a5f1e75cc1.tar.gz
openshift-711ba660dcfca9bb3739a5e45c4bc9a5f1e75cc1.tar.bz2
openshift-711ba660dcfca9bb3739a5e45c4bc9a5f1e75cc1.tar.xz
openshift-711ba660dcfca9bb3739a5e45c4bc9a5f1e75cc1.zip
bug 1468987: kibana_proxy OOM
We currently set the memory allocated to the kibana-proxy container to be the same as `max_old_space_size` for nodejs. But in V8, the heap consists of multiple spaces. The old space has only memory ready to be GC and measuring the used heap by kibana-proxy code, there is at least additional 32MB needed in the code space when `max_old_space_size` peaks. Setting the default memory limit to 256MB here and also changing the default calculation of `max_old_space_size` in the image repository to be only half of what the container receives to allow some heap for other `spaces`.
-rw-r--r--roles/openshift_logging_kibana/defaults/main.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/roles/openshift_logging_kibana/defaults/main.yml b/roles/openshift_logging_kibana/defaults/main.yml
index 23337bcd2..6b1c8531b 100644
--- a/roles/openshift_logging_kibana/defaults/main.yml
+++ b/roles/openshift_logging_kibana/defaults/main.yml
@@ -26,7 +26,7 @@ openshift_logging_kibana_ops_deployment: false
# Proxy settings
openshift_logging_kibana_proxy_debug: false
openshift_logging_kibana_proxy_cpu_limit: null
-openshift_logging_kibana_proxy_memory_limit: 96Mi
+openshift_logging_kibana_proxy_memory_limit: 256Mi
#The absolute path on the control node to the cert file to use
#for the public facing kibana certs