[ https://issues.apache.org/jira/browse/FLINK-32529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora closed FLINK-32529. ------------------------------ Resolution: Fixed merged to main 5ebfc5e4a6c31ea0c212f187bf7f7de70dfd1c09 > Optional startup probe for JM deployment > ---------------------------------------- > > Key: FLINK-32529 > URL: https://issues.apache.org/jira/browse/FLINK-32529 > Project: Flink > Issue Type: New Feature > Components: Kubernetes Operator > Reporter: Gyula Fora > Assignee: Gyula Fora > Priority: Major > Labels: pull-request-available > > There are certain cases where the JM enters a startup crash loop for example > due to incorrect HA config setup. With the current operator logic these cases > require manual user intervention as we don't have HA metadata available for > the last checkpoint and it also seems like the JM actually started already. > To solve this properly we suggest adding a default JM startup probe that > queries the rest api (/config) endpoint. -- This message was sent by Atlassian Jira (v8.20.10#820010)