You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Marios Trivyzas (Jira)" <ji...@apache.org> on 2022/02/08 11:24:00 UTC
[jira] [Created] (FLINK-26007) Use durationType instead of stringType for time related config options
Marios Trivyzas created FLINK-26007:
---------------------------------------
Summary: Use durationType instead of stringType for time related config options
Key: FLINK-26007
URL: https://issues.apache.org/jira/browse/FLINK-26007
Project: Flink
Issue Type: Improvement
Reporter: Marios Trivyzas
Check and change all relevant config options so that we have a well typed/defined type instead of parsing a string.
*NOTE:* This is a breaking change!
e.g.:
{noformat}
AkkaOptions#WATCH_HEARTBEAT_PAUSE
public static final ConfigOption<String> WATCH_HEARTBEAT_PAUSE =
ConfigOptions.key("akka.watch.heartbeat.pause")
.defaultValue("60 s")
.withDescription(
Description.builder()
.text(
"Acceptable heartbeat pause for Akka’s DeathWatch mechanism. A low value does not allow an"
+ " irregular heartbeat. If TaskManagers are wrongly marked dead because of lost or delayed"
+ " heartbeat messages, then you should increase this value or decrease akka.watch.heartbeat.interval."
+ " Higher value increases the time to detect a dead TaskManager. A thorough description of Akka’s"
+ " DeathWatch can be found %s",
link(
"http://doc.akka.io/docs/akka/snapshot/scala/remoting.html#failure-detector",
"here"))
.build());{noformat}
https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/configuration/AkkaOptions.java#L300
--
This message was sent by Atlassian Jira
(v8.20.1#820001)