Change Details

Today, we noticed that the flink-app-consumer-cloudelastic taskmanagers were down for about 16 hours. The flink jobmanager marked the job as FAILED, but the flink kubernetes operator did not try to start a new job. Creating this ticket to enable the feature via the `kubernetes.operator.job.restart` helm chart configuration value, as described in [[ https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/ | the Flink docs ]]

Today, we noticed that the flink-app-consumer-cloudelastic taskmanagers were down for about 16 hours. The flink jobmanager marked the job as FAILED, but the flink kubernetes operator did not try to start a new job. Creating this ticket to stabilize the service. Possible solutions include (but are not limited to): - Set the `kubernetes.operator.job.restart` flink-operator helm chart configuration value, as described in [[ https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/ | the Flink docs ]] - Allocate more RAM to consumer-cloudelastic taskManagers

Today, we noticed that the flink-app-consumer-cloudelastic taskmanagers were down for about 16 hours. The flink jobmanager marked the job as FAILED, but the flink kubernetes operator did not try to start a new job. Creating this ticket to enablstabilize the feature viae service. Possible solutions include (but are not limited to): - Set the `kubernetes.operator.job.restart` flink-operator helm chart configuration value, as described in [[ https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/ | the Flink docs ]] - Allocate more RAM to consumer-cloudelastic taskManagers