You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/03/21 08:46:00 UTC

[jira] [Created] (FLINK-26768) reconciliationStatus.error could not be cleared properly

Yang Wang created FLINK-26768:
---------------------------------

             Summary: reconciliationStatus.error could not be cleared properly
                 Key: FLINK-26768
                 URL: https://issues.apache.org/jira/browse/FLINK-26768
             Project: Flink
          Issue Type: Bug
          Components: Kubernetes Operator
            Reporter: Yang Wang


When testing the flink-kubernetes-operator, I find the {{reconciliationStatus.error}} could not be cleared properly. Even though, the job is running normally. It seems that {{reconciliationStatus.error}} could not be updated without spec change.
{code:java}
status:
  jobManagerDeploymentStatus: READY
  jobStatus:
    jobId: "00000000000000000000000000000000"
    jobName: State machine job
    savepointInfo: {}
    startTime: "1647851557367"
    state: RUNNING
    updateTime: "1647851870081"
  reconciliationStatus:
    error: back-off 5m0s restarting failed container=flink-main-container pod=flink-example-statemachine-6f76c78cd4-dvwnr_default(5ae2e615-8348-4536-8f37-05adf551bd53)
    lastReconciledSpec:
      flinkConfiguration:
        high-availability: org.apache.flink.kubernetes.highavailability.KubernetesHaServicesFactory
        high-availability.storageDir: file:///opt/flink/volume/flink-ha
        state.checkpoints.dir: file:///opt/flink/volume/flink-cp
        state.savepoints.dir: file:///opt/flink/volume/flink-sp
        taskmanager.numberOfTaskSlots: "2"
      flinkVersion: v1_14
      image: flink:1.14.3 {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)