[
https://issues.apache.org/jira/browse/FLINK-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978521#comment-15978521
]
Andrey commented on FLINK-6083:
-------------------------------
Currently we were able to create workaround by implementing `MetricReporter`
interface and starting ServerSocket to listen incoming commands. API similar to
https://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#The+Four+Letter+Words
> [TaskManager] Support readiness/liveness probes
> -----------------------------------------------
>
> Key: FLINK-6083
> URL: https://issues.apache.org/jira/browse/FLINK-6083
> Project: Flink
> Issue Type: New Feature
> Components: Distributed Coordination
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Andrey
>
> 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
(v6.3.15#6346)
