You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "yang gang (Jira)" <ji...@apache.org> on 2020/12/23 07:18:01 UTC

[jira] [Commented] (FLINK-20743) Print ContainerId For RemoteTransportException

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

yang gang commented on FLINK-20743:
-----------------------------------

[~zjwang] Hi.
Please see if this proposal is reasonable, thank you.

> Print ContainerId For RemoteTransportException
> ----------------------------------------------
>
>                 Key: FLINK-20743
>                 URL: https://issues.apache.org/jira/browse/FLINK-20743
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Network
>    Affects Versions: 1.10.0, 1.11.1, 1.12.1
>            Reporter: yang gang
>            Priority: Major
>         Attachments: image-2020-12-23-15-13-21-226.png
>
>
> !image-2020-12-23-15-13-21-226.png|width=970,height=291!
>  RemoteTransportException, this exception reminds the user which service has a problem by means of Ip/Port.
>  When we troubleshoot the problem, the information is not accurate enough. Usually at this time we need to look at the running log of the container that has the problem, but when we see this log, it also shows that the container has died, so pass Ip/ The port method can no longer quickly locate a specific container.
>  So I hope that when such an exception occurs, I hope to print the containerId。
> E.g:
>  Connection unexpectedly closed by remote task manager 'hostName/ip:port/containerId'. This might indicate that the remote task manager was lost.
>   
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)