elasticsearch Elasticsearch未知设置[xpack.license.self\u generated.type],elasticsearch,kubernetes,google-kubernetes-engine,elasticsearch,Kubernetes,Google Kubernetes Engine" /> elasticsearch Elasticsearch未知设置[xpack.license.self\u generated.type],elasticsearch,kubernetes,google-kubernetes-engine,elasticsearch,Kubernetes,Google Kubernetes Engine" />

elasticsearch Elasticsearch未知设置[xpack.license.self\u generated.type]

elasticsearch Elasticsearch未知设置[xpack.license.self\u generated.type],elasticsearch,kubernetes,google-kubernetes-engine,elasticsearch,Kubernetes,Google Kubernetes Engine,我正在将kubernetes集群上的elasticsearch从5.6.10升级到elasticsearch 6.1.4。然而,我甚至无法启动es 6.1.4 我不断收到错误未知设置[xpack.license.self\u generated.type] ,我尝试将该值设置为basic,xpack.license.self\u generated.type=basic,同时也忽略了该值 我见过其他一些人遇到这个错误,但他们的修复方法都不适合我 非常感谢您的帮助 我的状态集yaml apiVer

我正在将kubernetes集群上的elasticsearch从5.6.10升级到elasticsearch 6.1.4。然而,我甚至无法启动es 6.1.4

我不断收到错误
未知设置[xpack.license.self\u generated.type]

,我尝试将该值设置为basic,
xpack.license.self\u generated.type=basic
,同时也忽略了该值

我见过其他一些人遇到这个错误,但他们的修复方法都不适合我

非常感谢您的帮助

我的状态集yaml

apiVersion: apps/v1beta1
kind: StatefulSet
metadata:
  name: elastic-data
  labels:
    app: elastic-data
    area: devs
    role: nosql
    version: "6.1.4"
    environment: elastic
spec:
  serviceName: elastic-data
  replicas: 1
  updateStrategy:
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: elastic-data
        area: devs
        role: nosql
        version: "6.1.4"
        environment: elastic
      annotations:
        pod.beta.kubernetes.io/init-containers: '[
          {
          "name": "sysctl",
            "image": "busybox",
            "imagePullPolicy": "IfNotPresent",
            "command": ["sysctl", "-w", "vm.max_map_count=262144"],
            "securityContext": {
              "privileged": true
            }
          }
        ]'
    spec:
      terminationGracePeriodSeconds: 10
      securityContext:
        runAsUser: 1000
        fsGroup: 1000
      containers:
      - name: elastic-data
        image: docker.elastic.co/elasticsearch/elasticsearch:6.1.4
        resources:
          requests:
            memory: "512Mi"
          limits:
            memory: "1024Mi"
        env:
        - name: ES_JAVA_OPTS
          value: -Xms512m -Xmx512m
        command: ["/bin/bash", "-c", "~/bin/elasticsearch-plugin remove x-pack; elasticsearch"]
        args:
        - -Ecluster.name=elastic-devs
        - -Enode.name=${HOSTNAME}
        - -Ediscovery.zen.ping.unicast.hosts=elastic-master.default.svc.cluster.local
        - -Enode.master=false
        - -Enode.data=true
        - -Enode.ingest=false
        - -Enetwork.host=0.0.0.0
        - -Expack.license.self_generated.type=basic    
        ports:
        - containerPort: 9300
          name: transport
        - containerPort: 9200
          name: http
        volumeMounts:
        - name: data-volume
          mountPath: /usr/share/elasticsearch/data
        readinessProbe:
          tcpSocket:
            port: 9300
          initialDelaySeconds: 30
          periodSeconds: 30
          timeoutSeconds: 3
        livenessProbe:
          tcpSocket:
            port: 9300
          initialDelaySeconds: 30
          periodSeconds: 30
          timeoutSeconds: 3
  volumeClaimTemplates:
  - metadata:
      name: data-volume
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 2Gi

当他们试图通信时,您忘记从
config/elasticsearch.yml
中删除配置属性。因此,完整修订的
命令:

~/bin/elasticsearch-plugin remove x-pack
sed -i.bak -e /xpack.license.self_generated.type/d config/elasticsearch.yml
elasticsearch
别误会我的意思,他们为了不存在的东西轰炸配置属性是非常愚蠢的,但显然是这样的


p、 您可能更喜欢使用
--purge
选项,因为当我在本地尝试该命令时,
elasticsearch plugin
愉快地建议:

->在升级时保留插件配置文件[/usr/share/elasticsearch/config/x-pack];如果不需要,请使用--purge


因此:
/bin/elasticsearch plugin remove x-pack--purge

purge对我来说不起作用,但是你的第一个命令非常有效。谢谢你的帮助-你这个男人!