[
https://issues.apache.org/jira/browse/FLINK-21952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17345930#comment-17345930
]
Piotr Nowojski edited comment on FLINK-21952 at 5/17/21, 7:26 AM:
------------------------------------------------------------------
What about just using
{code:java}
if (cause.getMessage().contains("Connection reset by peer")) {
...
}
{code}
? Do you think it would cause some problems?
was (Author: pnowojski):
What about just using
{code:java}
if (cause.getMessage().contains("Connection reset by peer")) {
...
}
{code}
?
> 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)
