[
https://issues.apache.org/jira/browse/FLINK-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130635#comment-17130635
]
Till Rohrmann commented on FLINK-17579:
---------------------------------------
One thing to consider is that we wanted to add support for persistent volumes
and local recovery at some point which could vastly improve recovery speed of
Flink jobs. One idea how to solve the problem was to give TM processes a unique
and constant {{ResourceID}}. If now a TM is always started with the same
persistent volume, then we could achieve local recovery by simply redeploying
tasks to the TM with the same {{ResourceID}} as before. This could also work if
we only match on a unique and constant prefix of course. The important bit
would that we keep this idea in mind and try not to obstruct it if possible.
> Set the resource id of taskexecutor according to environment variable if
> exist in standalone mode
> -------------------------------------------------------------------------------------------------
>
> Key: FLINK-17579
> URL: https://issues.apache.org/jira/browse/FLINK-17579
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Yangze Guo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> Allow user to specify the resource id of TaskExecutor through the environment
> variable in standalone mode. The name of that variable could be
> {{FLINK_STANDALONE_TASK_EXECUTOR_ID}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
