Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ElasticSearch or Cluster-Logging Operator should extend the vm.max_map_count #336

Closed
jparrill opened this issue Jan 20, 2020 · 1 comment

Comments

@jparrill
Copy link

The kernel parameter regarding vm.max_map_count should be modified by Cluster-Logging-Operator or ElasticSearch Operator in order to allow deploy ElasticSearch instance correctly into the concrete project.

# Should be vm.max_map_count=262144
sysctl -n vm.max_map_count                          
65530
  • MC Patch
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  labels:
    machineconfiguration.openshift.io/role: master
  name: 99-sysctl-elastic
spec:
  config:
    ignition:
      version: 2.2.0
    storage:
      files:
      - contents:
          # vm.max_map_count=262144
          source: data:text/plain;charset=utf-8;base64,dm0ubWF4X21hcF9jb3VudD0yNjIxNDQ=
        filesystem: root
        mode: 0644
        path: /etc/sysctl.d/99-elasticsearch.conf
@jcantrill
Copy link
Contributor

This is done by the node tuning operator not CLO. This was as advised by arch team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants