[
https://issues.apache.org/jira/browse/FLINK-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128805#comment-17128805
]
Yang Wang commented on FLINK-17579:
-----------------------------------
[~azagrebin] [~karmagyz] Thanks for the fruitful discussion. First i want to
add more background of this ticket.
> Why the users want to specify the TaskManager instance name?
More and more users are deploying Flink in container environment, especially
K8s. When they have started a standalone session/job cluster, they need a
easier way to find the corresponding pod for a specific TaskManager. So then
they could tunnel in and debug the process(e.g. jmap).
> Use env or config option
I have no preference. Either of them makes sense to me. If we could provide a
unified approach to set Flink options via environment variables, it will be
great.
> How to generate the TaskManager name?
I think an config option whether to use {{hostname-uuid}} for TaskManager name
is enough. I agree that the uuid is necessary to avoid duplication. It could be
a short string, maybe 6 characters are enough. I am not sure whether
{{hostname-uuid}} is a too long string. In our production environment, the full
qualified hostname is usually no more than 45 characters(e.g.
xyz011177171118.na610.aliyun.com). In K8s, the podname could not be more than
63 characters. So i think maybe it is similar to Yarn container id(e.g.
container_e04_1591199811063_0665_01_000002).
All in all, providing a meaningful name for each TaskManager will make the log
more human readable and help with debugging.
> 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)
