You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ouyangwulin (Jira)" <ji...@apache.org> on 2020/01/19 03:08:00 UTC

[jira] [Commented] (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=17018771#comment-17018771 ] 

ouyangwulin commented on FLINK-15642:
-------------------------------------

Could assign this ticket for me?

> 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)