You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/07/04 08:57:00 UTC

[jira] [Created] (FLINK-32529) Optional startup probe for JM deployment

Gyula Fora created FLINK-32529:
----------------------------------

             Summary: 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


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)