[
https://issues.apache.org/jira/browse/FLINK-32814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752300#comment-17752300
]
Gyula Fora commented on FLINK-32814:
------------------------------------
In any case, this is indeed a very minor change so if you think that it
provides a reasonable value (and more than one user will actually use it :))
then we can add it.
Overall it's good to try limiting the number of configs available as they
anyways grow over time with new features. At the end we will have too much
> 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)
