[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505590#comment-14505590
]
ASF GitHub Bot commented on FLINK-1867:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/612#discussion_r28814392
--- Diff:
flink-tests/src/test/scala/org/apache/flink/api/scala/runtime/jobmanager/JobManagerFailsITCase.scala
---
@@ -136,9 +135,9 @@ with WordSpecLike with Matchers with BeforeAndAfterAll {
config.setInteger(ConfigConstants.TASK_MANAGER_NUM_TASK_SLOTS,
numSlots)
config.setInteger(ConfigConstants.LOCAL_INSTANCE_MANAGER_NUMBER_TASK_MANAGER,
numTaskmanagers)
config.setString(ConfigConstants.AKKA_WATCH_HEARTBEAT_INTERVAL, "1000
ms")
- config.setString(ConfigConstants.AKKA_WATCH_HEARTBEAT_PAUSE, "4000 ms")
+ config.setString(ConfigConstants.AKKA_WATCH_HEARTBEAT_PAUSE, "20 s")
--- End diff --
What is the effect of this setting on the test? Does it take very long now,
because the TaskManager needs really long to determine that the JobManager has
failed?
> TaskManagerFailureRecoveryITCase causes stalled travis builds
> -------------------------------------------------------------
>
> Key: FLINK-1867
> URL: https://issues.apache.org/jira/browse/FLINK-1867
> Project: Flink
> Issue Type: Bug
> Components: TaskManager, Tests
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Assignee: Aljoscha Krettek
>
> There are currently tests on travis failing:
> https://travis-ci.org/apache/flink/jobs/57943063
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
