[
https://issues.apache.org/jira/browse/FLINK-24945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijie Wang updated FLINK-24945:
-------------------------------
Description:
Currently, the exception location on WebUI only contains hostname and port, as
shown below:
!image-2021-11-18-14-40-39-855.png|width=638,height=188!
But in fact, we usually use ResourceID (ContainerID on yarn, PodID on
kubernetes) to locate the corresponding TM instead of hostname+port, so I think
the ResourceID should also be displayed here, which is more convenient for
users.
was:
Currently, the exception location on WebUI only contains hostname and port, as
shown below:
!image-2021-11-18-14-40-39-855.png|width=638,height=188!
But in fact, we usually use ResourceID (ContainerID on yarn, PodID on
kubernetes) to locate the corresponding TM instead of hostname+port, so I think
the resourceID should also be displayed here, which is more convenient for
users.
> The exception location on the WebUI should contain TM's ResourceID
> -------------------------------------------------------------------
>
> Key: FLINK-24945
> URL: https://issues.apache.org/jira/browse/FLINK-24945
> Project: Flink
> Issue Type: Improvement
> Reporter: Lijie Wang
> Priority: Major
> Attachments: image-2021-11-18-14-40-39-855.png
>
>
> Currently, the exception location on WebUI only contains hostname and port,
> as shown below:
> !image-2021-11-18-14-40-39-855.png|width=638,height=188!
> But in fact, we usually use ResourceID (ContainerID on yarn, PodID on
> kubernetes) to locate the corresponding TM instead of hostname+port, so I
> think the ResourceID should also be displayed here, which is more convenient
> for users.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
