[ 
https://issues.apache.org/jira/browse/FLINK-15642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-15642:
-----------------------------------
      Labels: auto-deprioritized-major  (was: stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> Support to set JobManager readiness and liveness check
> ------------------------------------------------------
>
>                 Key: FLINK-15642
>                 URL: https://issues.apache.org/jira/browse/FLINK-15642
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes
>            Reporter: Yang Wang
>            Priority: Minor
>              Labels: auto-deprioritized-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)

Reply via email to