You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2020/08/05 11:18:00 UTC
[jira] [Commented] (FLINK-16548) Expose consistent environment
variable to identify the component name and resource id of jm/tm
[ https://issues.apache.org/jira/browse/FLINK-16548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171427#comment-17171427 ]
Yangze Guo commented on FLINK-16548:
------------------------------------
After a second thought, I have some new points about this issue:
- It would be good to unify the TM's {{ResourceID}} from the environment.
- To identify the distributed component, I think users could achieve this by using {{containerized.master.env.}} and {{containerized.taskmanager.env.}}.
- Regarding exposing the {{ResourceID}} of JM, I'm not quite sure about that. Do we need to identify different JMs? How to define the {{ResourceID}} of JM? It could be the ResourceID of {{ResourceManager}} or {{JobMaster}}.
I think we can just unify the environment variable of TM id in this PR. WDYT? [~chinan.hjc][~fly_in_gis]
> Expose consistent environment variable to identify the component name and resource id of jm/tm
> ----------------------------------------------------------------------------------------------
>
> Key: FLINK-16548
> URL: https://issues.apache.org/jira/browse/FLINK-16548
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Configuration
> Reporter: hejianchao
> Priority: Major
> Fix For: 1.12.0
>
>
> We proposed to expose environment variable to identify the component name and resource id of jm/tm.
> To be specified:
> - Expose {{FLINK_COMPONENT_NAME}}. For jm, it should be "jobmanager". For tm, it should be "taskexecutor".
> - Expose {{FLINK_COMPONENT_ID}}. For jm/tm, it should be the resource id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)