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

**URL:** <https://discuss.elastic.co/t/the-cluster-phase-keep-invalid-when-i-upgrade-es-cluster-from-7-9-to-7-10/332639>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 5, 2023, 10:51am UTC](https://discuss.elastic.co/t/the-cluster-phase-keep-invalid-when-i-upgrade-es-cluster-from-7-9-to-7-10/332639 "2023-05-05T10:51:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![goodboyryan008](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goodboyryan008/32/120698_2.png) [@goodboyryan008](https://discuss.elastic.co/u/goodboyryan008)\
**Post date:** [May 5, 2023, 10:51am UTC](https://discuss.elastic.co/t/the-cluster-phase-keep-invalid-when-i-upgrade-es-cluster-from-7-9-to-7-10/332639/1 "2023-05-05T10:51:36Z")

</div>

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

```auto
# 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.

---

<div class="post-metadata">

**Author:** ![goodboyryan008](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goodboyryan008/32/120698_2.png) [@goodboyryan008](https://discuss.elastic.co/u/goodboyryan008)\
**Post date:** [May 6, 2023, 6:43am UTC](https://discuss.elastic.co/t/the-cluster-phase-keep-invalid-when-i-upgrade-es-cluster-from-7-9-to-7-10/332639/2 "2023-05-06T06:43:44Z")

</div>

how to see the invalid log? anywhere can see?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 3, 2023, 6:44am UTC](https://discuss.elastic.co/t/the-cluster-phase-keep-invalid-when-i-upgrade-es-cluster-from-7-9-to-7-10/332639/3 "2023-06-03T06:44:17Z")

</div>

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