[
https://issues.apache.org/jira/browse/FLINK-16288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045451#comment-17045451
]
Yang Wang commented on FLINK-16288:
-----------------------------------
[~nielsbasjes] Does the configuration option
{{resourcemanager.taskmanager-timeout}} make sense to you? It configure the
timeout for an idle task manager to be released, in milliseconds.
For the long term, we will support sidecar container for native K8s
integration. It could be used to collect logs to some external storage(S3,
elastic search, kafka, etc.).
> Setting the TTL for discarding task pods on Kubernetes.
> -------------------------------------------------------
>
> Key: FLINK-16288
> URL: https://issues.apache.org/jira/browse/FLINK-16288
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Niels Basjes
> Priority: Major
>
> I'm experimenting with running Flink 1.10.0 on native Kubernetes (version
> 1.17).
> After a job ends the task pods that were used to run it are discarded quite
> quickly.
> I found that if my job goes wrong I have too little time to look at all of
> the logs.
> I propose having a new config setting that allows me to run Flink on k8s
> where I can set the minimum time before an idle task pod is discarded.
> That way I can start Flink with a pod ttl of an hour (or something like that)
> so I have enough time to go through the logs and figure out what I did wrong.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
