Configure vm.max_map_count explicitly
This adds the mechanism to provide various other kernel parameters too. So it can be set for staging rancher nodes. It needs to be set to 262144 as a tryout elasticsearch will run there (and it's the minimum required for it to run properly). The remaining part of the changes is to unify with the current state of the infra. Most of the infra setting is set with the default value of 65530. Except for hypervisors and elastic nodes with value 262144, and cassandra nodes with value 1048575. Refs. swh/infra/sysadm-environment#4524
Showing
- data/common/cassandra.yaml 4 additions, 2 deletionsdata/common/cassandra.yaml
- data/common/common.yaml 4 additions, 0 deletionsdata/common/common.yaml
- data/hostname/beaubourg.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/beaubourg.softwareheritage.org.yaml
- data/hostname/branly.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/branly.softwareheritage.org.yaml
- data/hostname/esnode1.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/esnode1.internal.softwareheritage.org.yaml
- data/hostname/esnode2.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/esnode2.internal.softwareheritage.org.yaml
- data/hostname/esnode3.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/esnode3.internal.softwareheritage.org.yaml
- data/hostname/hypervisor3.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/hypervisor3.internal.softwareheritage.org.yaml
- data/hostname/mucem.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/mucem.internal.softwareheritage.org.yaml
- data/hostname/pompidou.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/pompidou.internal.softwareheritage.org.yaml
- data/hostname/rancher-node-staging-rke2-worker1.internal.staging.swh.network.yaml 3 additions, 0 deletions...de-staging-rke2-worker1.internal.staging.swh.network.yaml
- data/hostname/rancher-node-staging-rke2-worker2.internal.staging.swh.network.yaml 3 additions, 0 deletions...de-staging-rke2-worker2.internal.staging.swh.network.yaml
- data/hostname/rancher-node-staging-rke2-worker3.internal.staging.swh.network.yaml 3 additions, 0 deletions...de-staging-rke2-worker3.internal.staging.swh.network.yaml
- data/hostname/rancher-node-staging-rke2-worker4.internal.staging.swh.network.yaml 3 additions, 0 deletions...de-staging-rke2-worker4.internal.staging.swh.network.yaml
- data/hostname/search-esnode0.internal.staging.swh.network.yaml 3 additions, 0 deletions...hostname/search-esnode0.internal.staging.swh.network.yaml
- data/hostname/search-esnode4.internal.softwareheritage.org.yaml 4 additions, 0 deletions...ostname/search-esnode4.internal.softwareheritage.org.yaml
- data/hostname/search-esnode5.internal.softwareheritage.org.yaml 4 additions, 0 deletions...ostname/search-esnode5.internal.softwareheritage.org.yaml
- data/hostname/search-esnode6.internal.softwareheritage.org.yaml 4 additions, 0 deletions...ostname/search-esnode6.internal.softwareheritage.org.yaml
- data/hostname/somerset.internal.softwareheritage.org.yaml 4 additions, 0 deletionsdata/hostname/somerset.internal.softwareheritage.org.yaml
- site-modules/profile/manifests/base.pp 1 addition, 0 deletionssite-modules/profile/manifests/base.pp
Loading
Please register or sign in to comment