[
https://issues.apache.org/jira/browse/FLINK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220136#comment-16220136
]
ASF GitHub Bot commented on FLINK-7914:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/4903
Akka's default value is actually 5 seconds, which I think is a bit too high.
I actually tried to backtrack an instability in the `JobManagerFailsITCase`
and noticed that this test took roughly 16 s to execute (the ITCase contains
only 2 tests where we restart the JM). Part of the reason was that Akka gated
the JobManager ActorSystem for 5 seconds after we let the JM fail.
The actual solution to speed up this test was then to don't reuse the same
port for the new JobManager system, but I couldn't think of a good reason to
keep the 5 seconds default. Moreover, some other tests which also run into the
case of gated connections could also benefit from that. I think lowering the
gated interval should allow us to reestablish a lost connection faster.
> Expose Akka gated interval as user option
> -----------------------------------------
>
> Key: FLINK-7914
> URL: https://issues.apache.org/jira/browse/FLINK-7914
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.4.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
>
> Whenever Akka loses its connection to a remote {{ActorSystem}} it gates the
> corresponding address. The default value is {{5 s}}. Especially for tests
> this can be too high. Therefore, I propose to expose this option to the user
> via the {{AkkaOptions}} and setting it to {{50 ms}} per default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
