[
https://issues.apache.org/jira/browse/FLINK-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134718#comment-17134718
]
Till Rohrmann commented on FLINK-17579:
---------------------------------------
In the standalone case, users would need to use a third party tool to restart
the TMs. This tool would then have to set the right resource ids which should
be ok as long as we support setting some part of the resource id explicitly. I
believe this should be the case.
> 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)
