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

[BUG] elasticsearch cluster metrics component VolumeExpansion cluster always Updating #5730

Closed
JashBook opened this issue Nov 1, 2023 · 0 comments
Assignees
Labels
bug kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Milestone

Comments

@JashBook
Copy link
Collaborator

JashBook commented Nov 1, 2023

Describe the bug
elasticsearch cluster metrics component VolumeExpansion cluster always Updating.

To Reproduce
Steps to reproduce the behavior:

  1. create elasticsearch cluster
kbcli cluster create  esearch-wuftnw             --termination-policy=WipeOut             --monitoring-interval=0 --enable-all-logs=false --cluster-definition=elasticsearch --cluster-version=elasticsearch-8.8.2 --set cpu=500m,memory=1Gi,replicas=3,storage=20Gi  --namespace ns-ansapttxgp
  1. volume-expand metrics
kbcli cluster volume-expand esearch-wuftnw --auto-approve                 --components metrics                 --volume-claim-templates data                 --storage 21Gi --namespace ns-ansapttxgp 
  1. See error
`kbcli cluster volume-expand esearch-wuftnw --auto-approve                 --components metrics                 --volume-claim-templates data                 --storage 21Gi --namespace ns-ansapttxgp `
    
OpsRequest esearch-wuftnw-volumeexpansion-gznpx created successfully, you can view the progress:
	kbcli cluster describe-ops esearch-wuftnw-volumeexpansion-gznpx -n ns-ansapttxgp
check cluster status

      `kbcli cluster list esearch-wuftnw --show-labels  --namespace ns-ansapttxgp `
    
NAME             NAMESPACE       CLUSTER-DEFINITION   VERSION               TERMINATION-POLICY   STATUS     CREATED-TIME                 LABELS                                                                                                                                               
esearch-wuftnw   ns-ansapttxgp   elasticsearch        elasticsearch-8.8.2   WipeOut              Updating   Nov 01,2023 04:04 UTC+0000   app.kubernetes.io/instance=esearch-wuftnw,clusterdefinition.kubeblocks.io/name=elasticsearch,clusterversion.kubeblocks.io/name=elasticsearch-8.8.2   
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating
cluster_status:Updating

              [Error] check cluster status timeout
--------------------------------------get cluster esearch-wuftnw yaml--------------------------------------

      `kubectl get cluster esearch-wuftnw -o yaml  --namespace ns-ansapttxgp `
    
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
  annotations:
    kubeblocks.io/reconcile: "2023-11-01T04:23:40.914840181Z"
  creationTimestamp: "2023-11-01T04:04:37Z"
  finalizers:
  - cluster.kubeblocks.io/finalizer
  generation: 7
  labels:
    app.kubernetes.io/instance: esearch-wuftnw
    clusterdefinition.kubeblocks.io/name: elasticsearch
    clusterversion.kubeblocks.io/name: elasticsearch-8.8.2
  name: esearch-wuftnw
  namespace: ns-ansapttxgp
  resourceVersion: "57793"
  uid: 0a6cb0a3-cb22-48d5-aa02-df11660f062b
spec:
  affinity:
    podAntiAffinity: Preferred
    tenancy: SharedNode
  clusterDefinitionRef: elasticsearch
  clusterVersionRef: elasticsearch-8.8.2
  componentSpecs:
  - classDefRef:
      class: ""
    componentDefRef: elasticsearch
    monitor: false
    name: elasticsearch
    noCreatePDB: false
    replicas: 3
    resources:
      limits:
        cpu: 600m
        memory: 1536Mi
      requests:
        cpu: 600m
        memory: 1536Mi
    serviceAccountName: kb-esearch-wuftnw
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
  - classDefRef:
      class: ""
    componentDefRef: metrics
    monitor: false
    name: metrics
    noCreatePDB: false
    replicas: 3
    resources:
      limits:
        cpu: 600m
        memory: 1536Mi
      requests:
        cpu: 600m
        memory: 1536Mi
    serviceAccountName: kb-esearch-wuftnw
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 21Gi
  monitor: ***
  resources:
    cpu: "0"
    memory: "0"
  storage:
    size: "0"
  terminationPolicy: WipeOut
status:
  clusterDefGeneration: 2
  components:
    elasticsearch:
      phase: Running
      podsReady: true
      podsReadyTime: "2023-11-01T04:23:51Z"
    metrics:
      phase: Updating
      podsReady: false
      podsReadyTime: "2023-11-01T04:24:46Z"
  conditions:
  - lastTransitionTime: "2023-11-01T04:04:37Z"
    message: 'The operator has started the provisioning of Cluster: esearch-wuftnw'
    observedGeneration: 7
    reason: PreCheckSucceed
    status: "True"
    type: ProvisioningStarted
  - lastTransitionTime: "2023-11-01T04:12:52Z"
    message: Successfully applied for resources
    observedGeneration: 7
    reason: ApplyResourcesSucceed
    status: "True"
    type: ApplyResources
  - lastTransitionTime: "2023-11-01T04:24:55Z"
    message: 'pods are not ready in Components: [metrics], refer to related component
      message in Cluster.status.components'
    reason: ReplicasNotReady
    status: "False"
    type: ReplicasReady
  - lastTransitionTime: "2023-11-01T04:24:55Z"
    message: 'pods are unavailable in Components: [metrics], refer to related component
      message in Cluster.status.components'
    reason: ComponentsNotReady
    status: "False"
    type: Ready
  observedGeneration: 7
  phase: Updating
------------------------------------------------------------------------------------------------------------------
--------------------------------------describe cluster esearch-wuftnw--------------------------------------

      `kubectl describe cluster esearch-wuftnw  --namespace ns-ansapttxgp `
    
Name:         esearch-wuftnw
Namespace:    ns-ansapttxgp
Labels:       app.kubernetes.io/instance=esearch-wuftnw
              clusterdefinition.kubeblocks.io/name=elasticsearch
              clusterversion.kubeblocks.io/name=elasticsearch-8.8.2
Annotations:  kubeblocks.io/reconcile: 2023-11-01T04:23:40.914[840](https://github.com/apecloud/kubeblocks/actions/runs/6715331550/job/18250384107#step:11:841)181Z
API Version:  apps.kubeblocks.io/v1alpha1
Kind:         Cluster
Metadata:
  Creation Timestamp:  2023-11-01T04:04:37Z
  Finalizers:
    cluster.kubeblocks.io/finalizer
  Generation:        7
  Resource Version:  57793
  UID:               0a6cb0a3-cb22-48d5-aa02-df11660f062b
Spec:
  Affinity:
    Pod Anti Affinity:     Preferred
    Tenancy:               SharedNode
  Cluster Definition Ref:  elasticsearch
  Cluster Version Ref:     elasticsearch-8.8.2
  Component Specs:
    Class Def Ref:
      Class:            
    Component Def Ref:  elasticsearch
    Monitor:            false
    Name:               elasticsearch
    No Create PDB:      false
    Replicas:           3
    Resources:
      Limits:
        Cpu:     600m
        Memory:  1536Mi
      Requests:
        Cpu:               600m
        Memory:            1536Mi
    Service Account Name:  kb-esearch-wuftnw
    Volume Claim Templates:
      Name:  data
      Spec:
        Access Modes:
          ReadWriteOnce
        Resources:
          Requests:
            Storage:  20Gi
    Class Def Ref:
      Class:            
    Component Def Ref:  metrics
    Monitor:            false
    Name:               metrics
    No Create PDB:      false
    Replicas:           3
    Resources:
      Limits:
        Cpu:     600m
        Memory:  1536Mi
      Requests:
        Cpu:               600m
        Memory:            1536Mi
    Service Account Name:  kb-esearch-wuftnw
    Volume Claim Templates:
      Name:  data
      Spec:
        Access Modes:
          ReadWriteOnce
        Resources:
          Requests:
            Storage:  21Gi
  Monitor:
  Resources:
    Cpu:     0
    Memory:  0
  Storage:
    Size:              0
  Termination Policy:  WipeOut
Status:
  Cluster Def Generation:  2
  Components:
    Elasticsearch:
      Phase:            Running
      Pods Ready:       true
      Pods Ready Time:  2023-11-01T04:23:51Z
    Metrics:
      Phase:            Updating
      Pods Ready:       false
      Pods Ready Time:  2023-11-01T04:24:46Z
  Conditions:
    Last Transition Time:  2023-11-01T04:04:37Z
    Message:               The operator has started the provisioning of Cluster: esearch-wuftnw
    Observed Generation:   7
    Reason:                PreCheckSucceed
    Status:                True
    Type:                  ProvisioningStarted
    Last Transition Time:  2023-11-01T04:12:52Z
    Message:               Successfully applied for resources
    Observed Generation:   7
    Reason:                ApplyResourcesSucceed
    Status:                True
    Type:                  ApplyResources
    Last Transition Time:  2023-11-01T04:24:55Z
    Message:               pods are not ready in Components: [metrics], refer to related component message in Cluster.status.components
    Reason:                ReplicasNotReady
    Status:                False
    Type:                  ReplicasReady
    Last Transition Time:  2023-11-01T04:24:55Z
    Message:               pods are unavailable in Components: [metrics], refer to related component message in Cluster.status.components
    Reason:                ComponentsNotReady
    Status:                False
    Type:                  Ready
  Observed Generation:     7
  Phase:                   Updating
Events:
  Type     Reason                    Age                  From                Message
  ----     ------                    ----                 ----                -------
  Normal   ComponentPhaseTransition  28m (x2 over 28m)    cluster-controller  Create a new component
  Warning  Unhealthy                 26m (x5 over 26m)    event-controller    Pod esearch-wuftnw-elasticsearch-0: Startup probe failed: dial tcp 10.8.8.21:9200: connect: connection refused
  Warning  Unhealthy                 24m (x4 over 24m)    event-controller    Pod esearch-wuftnw-elasticsearch-1: Startup probe failed: dial tcp 10.8.6.17:9200: connect: connection refused
  Warning  Unhealthy                 21m (x6 over 22m)    event-controller    Pod esearch-wuftnw-elasticsearch-2: Startup probe failed: dial tcp 10.8.20.27:9200: connect: connection refused
  Warning  Unhealthy                 21m (x4 over 26m)    event-controller    Pod esearch-wuftnw-metrics-0: Readiness probe failed: Get "http://10.8.10.15:[911](https://github.com/apecloud/kubeblocks/actions/runs/6715331550/job/18250384107#step:11:912)4/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Normal   HorizontalScale           21m                  cluster-controller  start horizontal scale component elasticsearch of cluster esearch-wuftnw from 3 to 1
  Warning  ReplicasNotReady          21m (x2 over 27m)    cluster-controller  pods are not ready in Components: [elasticsearch], refer to related component message in Cluster.status.components
  Warning  ComponentsNotReady        21m (x2 over 27m)    cluster-controller  pods are unavailable in Components: [elasticsearch], refer to related component message in Cluster.status.components
  Normal   AllReplicasReady          20m (x2 over 21m)    cluster-controller  all pods of components are ready, waiting for the probe detection successful
  Normal   ClusterReady              20m (x2 over 21m)    cluster-controller  Cluster: esearch-wuftnw is ready, current phase is Running
  Normal   Running                   20m (x2 over 21m)    cluster-controller  Cluster: esearch-wuftnw is ready, current phase is Running
  Normal   PreCheckSucceed           19m (x3 over 28m)    cluster-controller  The operator has started the provisioning of Cluster: esearch-wuftnw
  Normal   ApplyResourcesSucceed     19m (x3 over 28m)    cluster-controller  Successfully applied for resources
  Normal   ComponentPhaseTransition  19m (x2 over 21m)    cluster-controller  component is Updating
  Warning  ReplicasNotReady          19m                  cluster-controller  pods are not ready in Components: [metrics], refer to related component message in Cluster.status.components
  Warning  ComponentsNotReady        19m                  cluster-controller  pods are unavailable in Components: [metrics], refer to related component message in Cluster.status.components
  Warning  Unhealthy                 17m (x5 over 18m)    event-controller    Pod esearch-wuftnw-elasticsearch-1: Startup probe failed: dial tcp 10.8.6.23:[920](https://github.com/apecloud/kubeblocks/actions/runs/6715331550/job/18250384107#step:11:921)0: connect: connection refused
  Warning  Unhealthy                 15m (x3 over 16m)    event-controller    Pod esearch-wuftnw-elasticsearch-2: Startup probe failed: dial tcp 10.8.16.35:9200: connect: connection refused
  Warning  Unhealthy                 11m                  event-controller    Pod esearch-wuftnw-elasticsearch-1: Startup probe failed: dial tcp 10.8.6.28:9200: connect: connection refused
  Normal   ComponentPhaseTransition  7m57s (x7 over 27m)  cluster-controller  component is Running
------------------------------------------------------------------------------------------------------------------

 `kbcli cluster list-ops esearch-wuftnw --status all  --namespace ns-ansapttxgp `
    
NAME                                   NAMESPACE       TYPE              CLUSTER          COMPONENT   STATUS    PROGRESS   CREATED-TIME                 
esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
ops_status:esearch-wuftnw-volumeexpansion-gznpx   ns-ansapttxgp   VolumeExpansion   esearch-wuftnw   metrics     Running   0/3        Nov 01,2023 04:24 UTC+0000   
check ops status timeout

Expected behavior
elasticsearch cluster metrics component VolumeExpansion success.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@JashBook JashBook added kind/bug Something isn't working severity/major Great chance user will encounter the same problem labels Nov 1, 2023
@JashBook JashBook added this to the Release 0.7.0 milestone Nov 1, 2023
@iziang iziang closed this as completed Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Projects
None yet
Development

No branches or pull requests

3 participants