[
https://issues.apache.org/jira/browse/FLINK-25402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567078#comment-17567078
]
jinghaihang commented on FLINK-25402:
-------------------------------------
Hi,Till Rohrmann [~trohrmann]
As the discription said:This is an optional feature that might not be usable
for all Flink deployments.
After read FLIP-198 & FLIP-201，I confuse that this feature can be used on Yarn
mode and how to confige a deterministic `taskmanager.resource-id` ?Or just suit
for k8s mode.
> FLIP-198: Working directory for Flink processes
> -----------------------------------------------
>
> Key: FLINK-25402
> URL: https://issues.apache.org/jira/browse/FLINK-25402
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> This issue implements
> [FLIP-198|https://cwiki.apache.org/confluence/x/ZZiqCw]. The idea is to
> introduce a working directory that can be used by Flink processes to store
> data that can be recovered if the process is restarted with access to the
> same working directory (e.g. via persistent volumes or restarting the process
> on the same node).
> The working directory will be default created in the temporary directory of
> the executing node. Moreover, the path will include the resource id of the
> Flink process. This will ensure that by default (random resource id), a newly
> started Flink process will see an empty working directory.
> This is an optional feature that might not be usable for all Flink
> deployments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
