[
https://issues.apache.org/jira/browse/FLINK-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393139#comment-16393139
]
ASF GitHub Bot commented on FLINK-8910:
---------------------------------------
GitHub user StefanRRichter opened a pull request:
https://github.com/apache/flink/pull/5676
[FLINK-8910][tests] Automated end-to-end test for local recovery and sticky
scheduling
This PR adds an automated end-to-end test for the local recovery feature,
which also includes sticky allocation. We expose allocation id through (not
public) `StreamingRuntimeContext `.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StefanRRichter/flink automated-test-finish
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/5676.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5676
----
commit 7de3d9d8ddaa84684e8c757285201387ad556ef2
Author: Stefan Richter <s.richter@...>
Date: 2018-03-08T18:20:32Z
[FLINK-8910][tests] Expose allocation id through runtime ctx
commit d8e740484a340f20277b9ed1e2d22b9d96897937
Author: Stefan Richter <s.richter@...>
Date: 2018-03-06T09:35:44Z
[FLINK-8910][tests] Automated test for local recovery (including sticky
allocation)
----
> 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: Test
> 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)
