{"id":825,"date":"2022-02-04T16:39:31","date_gmt":"2022-02-04T15:39:31","guid":{"rendered":"https:\/\/www.ume.li\/blog\/?p=825"},"modified":"2022-02-08T15:03:51","modified_gmt":"2022-02-08T14:03:51","slug":"hcl-component-pack-7-mulitple-namespaces-downsize","status":"publish","type":"post","link":"https:\/\/www.ume.li\/blog\/2022\/02\/04\/hcl-component-pack-7-mulitple-namespaces-downsize\/","title":{"rendered":"HCL Component Pack 7 – Mulitple Namespaces – downsize"},"content":{"rendered":"

For smaller environments it’s possible to downsize most of the containers to 1 instance. Except for redis, mongo and elasticsearch. Checking the statefulsets, redis requires 75M to 1G, mongo from 50M to 200M, elasticsearch from 3Gi to 4Gi.
\nReducing the pods for redis and mongo is not an option. <\/p>\n

Example scale for mw-proxy<\/p>\n

\r\nkubectl -n connections get deployments\r\nkubectl -n connections scale --replicas=1 deployment\/mw-proxy\r\n<\/pre>\n
So I focused on elasticsearch. There are 2 options. Reducing memory consumption and reducing the number of pods.
\nReduce the memory requirements can be achieved if you look at the helm chart.<\/p>\n
\r\nhelm show values elasticsearch7-0.1.0-20210427-114731.tgz  > elasticsearch.yml\r\n<\/pre>\n
There you get all the parameters that can be set by helm.<\/p>\n
So for my testenvironment I ended with this yaml file:<\/p>\n
\r\nclient:\r\n  ES_JAVA_OPTS_XMS: -Xms512m\r\n  ES_JAVA_OPTS_XMX: -Xmx512m\r\n  replicas: 2\r\n  resources:\r\n    limits:\r\n      cpu: '2'\r\n      mem: 2048Mi\r\n    requests:\r\n      cpu: '0.1'\r\n      mem: 1024Mi\r\ncommon:\r\n  storageClassName: nfs-client\r\n  storageSize: 8Gi\r\ndata:\r\n  ES_JAVA_OPTS_XMS: -Xms768m\r\n  ES_JAVA_OPTS_XMX: -Xmx768m\r\n  replicas: 2\r\n  resources:\r\n    limits:\r\n      cpu: '2'\r\n      mem: 4096Mi\r\n    requests:\r\n      cpu: '0.5'\r\n      mem: 2048Mi\r\nimage:\r\n  repository: harbor-lab.belsoft.ch:443\/connections\r\n  tag: 20210427-114731\r\nmaster:\r\n  ES_JAVA_OPTS_XMS: -Xms512m\r\n  ES_JAVA_OPTS_XMX: -Xmx512m\r\n  replicas: 2\r\n  resources:\r\n    limits:\r\n      cpu: '1'\r\n      mem: 1024Mi\r\n    requests:\r\n      cpu: '0.1'\r\n      mem: 512Mi\r\nnamespace: connect6\r\nnodeAffinityRequired: false\r\ncreateSecret: false\r\nrollingUpdate:\r\n  maxSurge: 1\r\n  maxUnavailable: 0\r\ntag: 20210427-114731\r\n<\/pre>\n
That’s just a first try, maybe it can be reduced even a bit more agressive.<\/p>\n
I used this to install the helm chart.
\n\"\"<\/a><\/p>\n
This setup requires some additional adjustments before you connect connections to elasticsearch: <\/p>\n
a) change the number of replicas for quickresults<\/a>. I reduced the es-data to 2 pods, so the replica count should be set to 1 (default is 2). If you don’t adjust this value, the index will have a yellow or red status.<\/p>\n
b) It might be usefull to reduce the shard counter <\/a>if you plan to use metrics.<\/p>\n
If you reduce the number of pods for elasticsearch after your indices have been created you may have a look at the index modules api<\/a> to bring your indices into a green state.<\/p>\n
After these modifications I’m down to 6.6G after restart.
\n\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
For smaller environments it’s possible to downsize most of the containers to 1 instance. Except for redis, mongo and elasticsearch.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[62,54,23],"tags":[67,24,73],"class_list":["post-825","post","type-post","status-publish","format-standard","hentry","category-62","category-component-pack","category-connections","tag-component-pack","tag-connections","tag-downsize"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t