flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yun Gao (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-21952) Make all the "Connection reset by peer" exception wrapped as RemoteTransportException
Date Thu, 20 May 2021 04:18:00 GMT

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

Yun Gao commented on FLINK-21952:
---------------------------------

Hi [~pnowojski] Very sorry for missing the notification and response later.  I think it
works since the exception might be caught here are all thrown by the downstream task Netty
stack, and their kinds are limited, thus directly distinguish them via keywords should be
enough.

> Make all the "Connection reset by peer" exception wrapped as RemoteTransportException
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-21952
>                 URL: https://issues.apache.org/jira/browse/FLINK-21952
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Network
>            Reporter: Yun Gao
>            Priority: Major
>              Labels: stale-major
>
> In CreditBasedPartitionRequestClientHandler#exceptionCaught, the IOException or the exception
with exact message "Connection reset by peer" are marked as RemoteTransportException. 
> However, with the current Netty implementation, sometimes it might throw 
> {code:java}
> org.apache.flink.shaded.netty4.io.netty.channel.unix.Errors$NativeIoException: readAddress(..)
failed: Connection reset by peer
> {code}
> in some case. It would be also wrapped as LocalTransportException, which might cause
some confusion. 



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

Mime
View raw message