[
https://issues.apache.org/jira/browse/FLINK-20743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20743:
-----------------------------------
Labels: auto-unassigned stale-minor (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-unassigned, stale-minor
> 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.20.1#820001)
