[
https://issues.apache.org/jira/browse/FLINK-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber updated FLINK-9785:
-------------------------------
Description:
{{LocalTransportException}} instantiations do not always add the remote address
into the exception message. Having this will ease debugging and make
correlating different log files much easier.
There always is an address associated with these exceptions but it does not
seem like this is used anywhere for now and in that case it is also the local
address (looks like its intended to be the error source's address).
was:{{TransportException}} instantiations do not always add the remote
address into the exception message. This is especially true for the
{{LocalTransportException}}. There always is an address associated with these
exceptions but it does not seem like this is used anywhere for now.
> Add remote addresses to LocalTransportException instances
> ---------------------------------------------------------
>
> Key: FLINK-9785
> URL: https://issues.apache.org/jira/browse/FLINK-9785
> Project: Flink
> Issue Type: Improvement
> Components: Network
> Affects Versions: 1.5.0, 1.4.2
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Fix For: 1.6.0
>
>
> {{LocalTransportException}} instantiations do not always add the remote
> address into the exception message. Having this will ease debugging and make
> correlating different log files much easier.
> There always is an address associated with these exceptions but it does not
> seem like this is used anywhere for now and in that case it is also the local
> address (looks like its intended to be the error source's address).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
