如何在Kubernetes上禁用Elasticsearch中的交换？

Question

根据official es docs，禁用交换是Elasticsearch可用的最佳性能提升之一。

但是，它被证明很难配置。我花了几个小时研究和尝试使用Kubernetes上的官方ES docker镜像禁用交换的不同方法。

将bootstrap.memory_lock: true设置为env变量时，图像无法启动时出现错误：Unable to lock JVM Memory: error=12, reason=Cannot allocate memory. This can result in part of the JVM being swapped out. Increase RLIMIT_MEMLOCK, soft limit: 65536, hard limit: 65536。正如文档所指出的那样，这是预期的。我甚至用设置安装了一个自定义的/etc/security/limits.conf，但那是失败的。

在k8s上使用官方es图像时，建议禁用交换的方法是什么？

而且，这是我的yaml的相关部分

apiVersion: apps/v1beta1
kind: StatefulSet
metadata:
  name: elastic-data
spec:
  serviceName: elastic-data
  replicas: 1
  template:
    spec:
      securityContext:
        runAsUser: 0
        fsGroup: 0
      containers:
      - name: elastic-data
        image: docker.elastic.co/elasticsearch/elasticsearch-oss:6.4.0
        env:
        - name: ES_JAVA_OPTS
          value: "-Xms2g -Xmx2g"
        - name: cluster.name
          value: "elastic-devs"
        - name: node.name
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: discovery.zen.ping.unicast.hosts
          value: "elastic-master.default.svc.cluster.local"
        - name: node.master
          value: "false"
        - name: node.ingest
          value: "false"
        - name: node.data
          value: "true"
        - name: network.host
          value: "0.0.0.0"
        - name: path.data
          value: /usr/share/elasticsearch/data
        - name: indices.memory.index_buffer_size
          value: "512MB"
        - name: bootstrap.memory_lock
          value: "true"
        resources:
          requests:
            memory: "3Gi"
          limits:
            memory: "3Gi"
        ports:
        - containerPort: 9300
          name: transport
        - containerPort: 9200
          name: http
        volumeMounts:
        - name: data-volume
          mountPath: /usr/share/elasticsearch/data
        - name: swappiness-config
          mountPath: /etc/security/limits.conf
          subPath: limits.conf
      volumes:
      - name: data-volume
        persistentVolumeClaim:
          claimName: pvc-es
     - name: swappiness-config
       configMap:
         name: swappiness-config
         items:
          - key: limits.conf
             path: limits.conf

limits.conf中

elasticsearch soft memlock unlimited
elasticsearch hard memlock unlimited
elasticsearch hard nofile 65536
elasticsearch soft nofile 65536

Answer 1

我想，我的yaml中的ulimits没有被识别，所以我跟着this post创建了一个带有自定义入口点的图像来设置设置。

Answer 2

你使用哪种图像类型？如果其容器优化的操作系统（cos）尝试切换到基于Ubuntu的图像