[
https://issues.apache.org/jira/browse/FLINK-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853990#comment-15853990
]
ASF GitHub Bot commented on FLINK-4449:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/2791#discussion_r99582774
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/taskexecutor/TaskExecutorRegistrationSuccess.java
---
@@ -33,16 +34,21 @@
private final InstanceID registrationId;
+ private final ResourceID resourceManagerIdentify;
+
private final long heartbeatInterval;
/**
* Create a new {@code TaskExecutorRegistrationSuccess} message.
- *
- * @param registrationId The ID that the ResourceManager assigned
the registration.
- * @param heartbeatInterval The interval in which the ResourceManager
will heartbeat the TaskExecutor.
+ *
+ * @param registrationId The ID that the ResourceManager
assigned the registration.
+ * @param resourceManagerIdentify The identify of the ResourceManager,
for heartbeat
--- End diff --
`resourceManagerId`
> Heartbeat Manager integration with TaskExecutor
> -----------------------------------------------
>
> Key: FLINK-4449
> URL: https://issues.apache.org/jira/browse/FLINK-4449
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: zhangjing
> Assignee: zhangjing
>
> ResourceManager need a heartbeat manager to monitor the connections with all
> registered TaskExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
