[
https://issues.apache.org/jira/browse/FLINK-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424024#comment-16424024
]
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_r178824035
--- Diff:
flink-core/src/main/java/org/apache/flink/api/common/TaskInfo.java ---
@@ -107,4 +131,12 @@ public int getAttemptNumber() {
public String getTaskNameWithSubtasks() {
return this.taskNameWithSubtasks;
}
+
+ /**
+ * Returns the allocation id for where this task is executed.
+ * @return the allocation id for where this task is executed.
+ */
+ public String getAllocationID() {
--- End diff --
Hmm, what about testing it a bit more indirectly, by removing the
checkpoint files on the DFS. Then you can only recover if you recover locally.
Or by querying the REST interface? We might have to add the information to the
`VertexTaskDetail`.
Otherwise, we start mixing concerns and expose unnecessary information to
the user via the `AbstractRuntimeUDFContext`. Moreover, not every function has
access to this information right now. For example the
`RichAsyncFunctionRuntimeContext` does not expose it.
> 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)
