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 2019/09/27 09:50:00 UTC

[jira] [Closed] (FLINK-6083) [TaskManager] Support readiness/liveness probes

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

Till Rohrmann closed FLINK-6083.
--------------------------------
    Resolution: Invalid

No longer valid with Flip-6 changes. A {{TaskExecutor}} now connects to the {{ResourceManager}}.

> [TaskManager] Support readiness/liveness probes
> -----------------------------------------------
>
>                 Key: FLINK-6083
>                 URL: https://issues.apache.org/jira/browse/FLINK-6083
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Coordination
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Andrey
>            Priority: Major
>
> Currently there is no way to tell if TaskManager is operating or not. Operating means "its connected to JobManager and ready to process requests". 
> TaskManager should provide metric "jobManagerConnection":
> * 0 - disconnected
> * 1 - connected
> Or any other API which could expose connection status.
> Expected usage:
> * run task manager in managed environment
> * configure readiness and liveness probes (periodically poll jmx or REST)
> * restart task manager if liveness probe returns 0 (disconnected)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)