The cluster PHASE keep Invalid when I upgrade es cluster from 7.9 to 7.10

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

hey, budies,
i have no idea which thing goes wrong. any ideas

# Source: eck-operator-crds/templates/all-crds.yaml
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: es7-cluster
  namespace: abc
spec:
  version: 7.10.1
  nodeSets:
  - name: master
    count: 3
    config:
      
      node.roles: ["master"]
      xpack.ml.enabled: true
      
    podTemplate:
      spec:
        affinity:
          nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
              nodeSelectorTerms:
              - matchExpressions:
                - key: xes-nodegroup/app
                  operator: Exists
          podAntiAffinity:
            preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 100
              podAffinityTerm:
                labelSelector:
                  matchLabels:
                    elasticsearch.k8s.elastic.co/cluster-name: es7-cluster
                topologyKey: kubernetes.io/hostname
        initContainers:
        - name: sysctl
          securityContext:
            privileged: true
          command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144']
        containers:
        - name: elasticsearch
          env:
          - name: ES_JAVA_OPTS
            value: -Xms18g -Xmx18g
          resources:
            requests:
              cpu: 1
              memory: 35Gi
            limits:
              cpu: 16
              memory: 72Gi
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 200Gi
        storageClassName: standard
- name: data
    count: 2
    config:
      
      node.roles: ["data", "data_hot", "ingest", "ml", "transform"]
      node.attr.zone: hot
      script.max_compilations_rate: 150/5m
      
    podTemplate:
      spec:
        affinity:
          nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
              nodeSelectorTerms:
              - matchExpressions:
                - key: xes-nodegroup/app
                  operator: Exists
          podAntiAffinity:
            preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 100
              podAffinityTerm:
                labelSelector:
                  matchLabels:
                    elasticsearch.k8s.elastic.co/cluster-name: es7-cluster
                topologyKey: kubernetes.io/hostname
        initContainers:
        - name: sysctl
          securityContext:
            privileged: true
          command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144']
        containers:
        - name: elasticsearch
          env:
          - name: ES_JAVA_OPTS
            value: -Xms18g -Xmx18g
          resources:
            requests:
              cpu: 1
              memory: 35Gi
            limits:
              cpu: 16
              memory: 72Gi
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 2000Gi
        storageClassName: standard

thanks all.

2

how to see the invalid log? anywhere can see?

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.