[jboss-jira] [JBoss JIRA] (SWSQE-203) Apply "sysctl -w vm.max_map_count=262144 " to B12 cluster
[
https://issues.jboss.org/browse/SWSQE-203?page=com.atlassian.jira.plugin....
]
Guilherme Baufaker Rêgo commented on SWSQE-203:
-----------------------------------------------
Applied to all nodes of the cluster.
ssh root(a)b12.jonqe.lab.eng.bos.redhat.com
✔ 10023 09:55:18
Last login: Wed Apr 25 18:30:13 2018 from 10.97.116.68
[root@b12 ~]# oc get nodes
NAME STATUS ROLES AGE VERSION
b11.jonqe.lab.eng.bos.redhat.com Ready compute 23d v1.9.1+a0ce1bc657
b12.jonqe.lab.eng.bos.redhat.com Ready master 23d v1.9.1+a0ce1bc657
b14.jonqe.lab.eng.bos.redhat.com Ready compute 11d v1.9.1+a0ce1bc657
[root@b12 ~]# sudo sysctl -w vm.max_map_count=262144
vm.max_map_count = 262144
[root@b12 ~]# exit
logout
Connection to b12.jonqe.lab.eng.bos.redhat.com closed.
gbaufake@lenovo-t460 ~ ssh root(a)b11.jonqe.lab.eng.bos.redhat.com
✔ 10024 09:55:55
Last login: Wed Apr 25 10:28:48 2018 from 10.97.116.68
[root@b11 ~]# sudo sysctl -w vm.max_map_count=262144
vm.max_map_count = 262144
[root@b11 ~]# exit
logout
Connection to b11.jonqe.lab.eng.bos.redhat.com closed.
gbaufake@lenovo-t460 ~ ssh root(a)b14.jonqe.lab.eng.bos.redhat.com
✔ 10025 09:56:05
Last login: Mon Apr 30 11:39:01 2018 from 10.97.116.15
[root@b14 ~]# sudo sysctl -w vm.max_map_count=262144
vm.max_map_count = 262144
Apply "sysctl -w vm.max_map_count=262144 " to B12 cluster
---------------------------------------------------------
Key: SWSQE-203
URL: https://issues.jboss.org/browse/SWSQE-203
Project: Kiali QE
Issue Type: QE Task
Reporter: Kevin Earls
Assignee: Guilherme Baufaker Rêgo
As part of https://issues.jboss.org/browse/SWSQE-113 the command "sudo sysctl -w
vm.max_map_count=262144 " was executed on the B12 cluster in order to allow
ElasticSearch to run correctly.
However I tried to run a performance test this morning and the ES deployment failed with
ERROR: [1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least
[262144]
Can you reapply this and do whatever is needed to make sure it persists over cluster
rebuilds or restarts? Thanks.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)