You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2022/11/22 09:16:00 UTC

[jira] [Comment Edited] (FLINK-29639) Add ResourceId in TransportException for debugging

    [ https://issues.apache.org/jira/browse/FLINK-29639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635612#comment-17635612 ] 

Xintong Song edited comment on FLINK-29639 at 11/22/22 9:15 AM:
----------------------------------------------------------------

- master (1.17): 93c834be953f1336adb3ec5b5bf759a20e25eddf
- release-1.16: df061627591a1f62942e0700d51bb79259fb8f54
- release-1.15: 7a4fb7c86fbb28bee63bba829ebdda7b886170e3


was (Author: xintongsong):
master (1.17): 93c834be953f1336adb3ec5b5bf759a20e25eddf

> Add ResourceId in TransportException for debugging 
> ---------------------------------------------------
>
>                 Key: FLINK-29639
>                 URL: https://issues.apache.org/jira/browse/FLINK-29639
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Liu
>            Assignee: Weijie Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.17.0
>
>
> When the taskmanager is lost, only the host and port are shown in the exception. It is hard to find the exactly taskmanger by resourceId. Add ResourceId info will help a lot in debugging the job.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)