[
https://issues.apache.org/jira/browse/FLINK-32814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752170#comment-17752170
]
Yaroslav Tkachenko commented on FLINK-32814:
--------------------------------------------
[~gyfora] true! I had to set it to 1 year.
Still, it feels hacky. There are many ".enabled" config options to control
other features, so I think adding one for terminal JM shutdown is justifiable.
I submitted a PR for this.
> Support disabling failed JM shutdown in the operator
> ----------------------------------------------------
>
> Key: FLINK-32814
> URL: https://issues.apache.org/jira/browse/FLINK-32814
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.5.0
> Reporter: Yaroslav Tkachenko
> Priority: Major
> Labels: pull-request-available
>
> Currently, it's not possible to disable the shutdown of the jobmanager pods
> in a terminal state, e.g. {*}FAILED{*}. I may want to keep failed jobmanager
> pods around until they should be deleted explicitly, e.g. after an
> investigation.
> The TTL for the shutdown is controlled by the
> *kubernetes.operator.jm-deployment.shutdown-ttl* option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
