[
https://issues.apache.org/jira/browse/FLINK-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132864#comment-17132864
]
Yangze Guo commented on FLINK-17579:
------------------------------------
Thanks for the feedback, [~trohrmann], [~fly_in_gis] and [~azagrebin].
Here are some of my thoughts:
- Since I do not see any drawback or regression in using {{hostname-uuid}} as
the {{ResourceID}}, I think it probably makes sense to just change the default
behavior. We may not need a config option for it.
- Regarding Till's concern, I think it would not obstruct it because, in
Kubernetes scenario, the {{hostname}} is unique and constant. Correct me if I
mistake [~fly_in_gis].
- However, it may not work in standalone scenario since the {{hostname}} is not
ensured to be unique. Do we also plan to support local recovery in standalone
mode? [~trohrmann]
> 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)
