You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/02/28 15:47:00 UTC
[jira] [Resolved] (FLINK-16288) Setting the TTL for discarding task
pods on Kubernetes.
[ https://issues.apache.org/jira/browse/FLINK-16288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-16288.
-----------------------------------
Fix Version/s: 1.11.0
1.10.1
Resolution: Fixed
Fixed via
1.11.0: 8c063d30666a5089fb09485148c1284e49c39c37
1.10.1: 21c47adc44b2890902cd9ca220e99e7071d2671b
> 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
> Assignee: Niels Basjes
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.1, 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)