You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "duchen (Jira)" <ji...@apache.org> on 2020/01/19 05:47:00 UTC
[jira] [Comment Edited] (FLINK-15642) Support to set JobManager
liveness check
[ https://issues.apache.org/jira/browse/FLINK-15642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018793#comment-17018793 ]
duchen edited comment on FLINK-15642 at 1/19/20 5:46 AM:
---------------------------------------------------------
Can assign https://issues.apache.org/jira/browse/FLINK-15642 for me, i'm very interested!
[~fly_in_gis]
was (Author: duchen):
Can assign https://issues.apache.org/jira/browse/FLINK-15642 for me, i'm very interested!
> Support to set JobManager liveness check
> ----------------------------------------
>
> Key: FLINK-15642
> URL: https://issues.apache.org/jira/browse/FLINK-15642
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Reporter: Yang Wang
> Priority: Major
>
> The liveness of TaskManager will be controlled by Flink Master. When it failed, timeout, a new pod will be started to replace. We need to add a liveness check for JobManager.
>
> It just like what we could do in the yaml.
> {code:java}
> ...
> livenessProbe:
> tcpSocket:
> port: 6123
> initialDelaySeconds: 30
> periodSeconds: 60
> ...{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)