[
https://issues.apache.org/jira/browse/FLINK-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406597#comment-16406597
]
ASF GitHub Bot commented on FLINK-8910:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/5676#discussion_r175812511
--- Diff: flink-end-to-end-tests/test-scripts/common.sh ---
@@ -176,10 +176,40 @@ function s3_delete {
https://${bucket}.s3.amazonaws.com/${s3_file}
}
+function tm_watchdog {
+ expectedTm=$1
+ while true;
+ do
+ runningTm=`jps | grep -o 'TaskManagerRunner' | wc -l`;
+ count=$((expectedTm-runningTm))
+ for (( c=0; c<count; c++ ))
+ do
+ $FLINK_DIR/bin/taskmanager.sh start > /dev/null
+ done
+ sleep 5;
+ done
+}
+
+function jm_kill_all {
+ kill_all StandaloneSessionClusterEntrypoint
+}
+
+function tm_kill_all {
+ kill_all TaskManagerRunner
--- End diff --
Same here
> Introduce automated end-to-end test for local recovery (including sticky
> scheduling)
> ------------------------------------------------------------------------------------
>
> Key: FLINK-8910
> URL: https://issues.apache.org/jira/browse/FLINK-8910
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Affects Versions: 1.5.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Fix For: 1.5.0
>
>
> We should have an automated end-to-end test that can run nightly to check
> that sticky allocation and local recovery work as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
