[
https://issues.apache.org/jira/browse/FLINK-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516216#comment-15516216
]
ASF GitHub Bot commented on FLINK-4606:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2543
The linked JIRA issue seems to be wrong.
I'm not completely sure whether we want to add this functionality to the
`RpcService` or not. At the moment it is easy to implement because we can rely
on Akka's death watch functionality. But future implementations might work
differently. Thus, we would be bound to reimplement the death watch
functionality.
Furthermore, once a target actor system has been marked as "dead" by the
deathwatch it will be quarantined. If it was marked wrongly, then there is no
way for the target actor system to talk to the watching system and vice versa.
What's the benefit over having a separate service for the heartbeat like it
is done in #2435?
> Integrate the new ResourceManager with the existing FlinkResourceManager
> ------------------------------------------------------------------------
>
> Key: FLINK-4606
> URL: https://issues.apache.org/jira/browse/FLINK-4606
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: zhangjing
> Assignee: zhangjing
>
> Integrate the new ResourceManager with the existing FlinkResourceManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
