You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Danny Cranmer (Jira)" <ji...@apache.org> on 2022/10/21 17:58:00 UTC
[jira] [Commented] (FLINK-29713) Kubernetes operator should restart failed jobs
[ https://issues.apache.org/jira/browse/FLINK-29713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622391#comment-17622391 ]
Danny Cranmer commented on FLINK-29713:
---------------------------------------
Did you try using the job restart strategy? [https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#restart-strategy-type]
Does not cover the reconfiguration but will restart failed jobs
> Kubernetes operator should restart failed jobs
> ----------------------------------------------
>
> Key: FLINK-29713
> URL: https://issues.apache.org/jira/browse/FLINK-29713
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Fix For: kubernetes-operator-1.3.0
>
>
> It would be good to have the possibility to restart the Flink Application if it goes to {{FAILED}} state.
> This could be used to restart, and reconfigure the job dynamically in the application {{main}} method if the current application can not handle the incoming data
--
This message was sent by Atlassian Jira
(v8.20.10#820010)