[
https://issues.apache.org/jira/browse/FLINK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882735#comment-15882735
]
ASF GitHub Bot commented on FLINK-4364:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/3151#discussion_r102753723
--- Diff:
flink-core/src/main/java/org/apache/flink/configuration/ConfigConstants.java ---
@@ -703,6 +703,18 @@
* Exit JVM on fatal Akka errors
*/
public static final String AKKA_JVM_EXIT_ON_FATAL_ERROR =
"akka.jvm-exit-on-fatal-error";
+
+ // ----------------------------- Heartbeat Settings
-----------------------
+
+ /**
+ * Timeout for requesting and receiving heartbeat for both sender and
receiver sides
+ */
+ public static final String HEARTBEAT_TIMEOUT = "heartbeat.timeout";
+
+ /**
+ * Time interval for requesting heartbeat from sender side
+ */
+ public static final String HEARTBEAT_INTERVAL = "heartbeat.interval";
--- End diff --
The community decided to move away from the `ConfigConstants` in favour of
`ConfigOptions`. See `HighAvailabilityOptions` to see how they are defined and
used.
> Implement TaskManager side of heartbeat from JobManager
> -------------------------------------------------------
>
> Key: FLINK-4364
> URL: https://issues.apache.org/jira/browse/FLINK-4364
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: zhijiang
> Assignee: zhijiang
>
> The {{JobManager}} initiates heartbeat messages via (JobID, JmLeaderID), and
> the {{TaskManager}} will report metrics info for each heartbeat.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
