[
https://issues.apache.org/jira/browse/FLINK-26274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502212#comment-17502212
]
Chesnay Schepler edited comment on FLINK-26274 at 3/7/22, 11:54 AM:
--------------------------------------------------------------------
There is a bug somewhere in the resource requirement handling.
The job starts out with a requirement of 6 slots with the UNKNOWN resource
profile (which is expected, because it doesn't care what resources the slot
actually provides), and then starts duplicating the requirements with a more
specific resource profile (the default profile that the TM comes up with).
was (Author: zentol):
There is a bug somewhere. The DeclarativeSlotPoolBridge uses the wrong resource
profile for the slots it has acquired.
> Test local recovery works across TaskManager process restarts
> -------------------------------------------------------------
>
> Key: FLINK-26274
> URL: https://issues.apache.org/jira/browse/FLINK-26274
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Till Rohrmann
> Assignee: Dawid Wysakowicz
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.15.0
>
> Attachments: jobmanager_local_restore_2.log
>
>
> This ticket is a testing task for
> [FLIP-201|https://cwiki.apache.org/confluence/x/wJuqCw].
> When enabling local recovery and configuring a working directory that can be
> re-read after a process failure, Flink should now be able to recover locally.
> We should test whether this is the case. Please take a look at the
> documentation [1, 2] to see how to configure Flink to make use of it.
> [1]
> https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/standalone/working_directory/
> [2]
> https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/standalone/kubernetes/#enabling-local-recovery-across-pod-restarts
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
