flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Kruber (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-9785) Add remote addresses to LocalTransportException instances
Date Thu, 12 Jul 2018 10:03:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nico Kruber resolved FLINK-9785.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.2

Fixed via
1.6.0: 9e87e2030d5a8232b80e6dbb93166fb9ac9ecb53
1.5.2: 2a24c27771d9fb30ad710889d32290ba23d7f10b

> 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
>              Labels: pull-request-available
>             Fix For: 1.5.2, 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)

Mime
View raw message