[
https://issues.apache.org/jira/browse/FLINK-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135451#comment-17135451
]
Yangze Guo commented on FLINK-17579:
------------------------------------
Yes, I think it could work. So, it seems that it is still necessary to allow
the user to set an arbitrary prefix.
To summarize, the proposed changes are:
- Add a config option "taskmanager.resource-id.prefix".
- In standalone mode, if "taskmanager.resource-id.prefix" is defined, the
{{ResourceID}} of the {{taskexecutor}} should be {{prefix-uuid}}.
WDYT? [~trohrmann][~azagrebin][~fly_in_gis]
> 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)
