You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Thomas Weise (Jira)" <ji...@apache.org> on 2022/03/14 04:25:00 UTC

[jira] [Assigned] (FLINK-26538) Ability to restart deployment w/o spec change

     [ https://issues.apache.org/jira/browse/FLINK-26538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Weise reassigned FLINK-26538:
------------------------------------

    Assignee: Aitozi

> Ability to restart deployment w/o spec change
> ---------------------------------------------
>
>                 Key: FLINK-26538
>                 URL: https://issues.apache.org/jira/browse/FLINK-26538
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kubernetes Operator
>            Reporter: Thomas Weise
>            Assignee: Aitozi
>            Priority: Major
>
> Operator should allow restart of the Flink deployment w/o any other spec change. This provides the escape hatch for an operator to recover a deployment that has gone into a bad state (for whatever reason including memory leaks, hung JVM etc.) without direct access to the k8s cluster. This can be addressed by adding a restartNonce to the CRD.
>  



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