You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Brown (JIRA)" <ji...@apache.org> on 2017/08/19 01:23:01 UTC
[jira] [Comment Edited] (CASSANDRA-13649) Uncaught exceptions in
Netty pipeline
[ https://issues.apache.org/jira/browse/CASSANDRA-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133434#comment-16133434 ]
Jason Brown edited comment on CASSANDRA-13649 at 8/19/17 1:22 AM:
------------------------------------------------------------------
I'm +1 on the patch, and I'll setup a branch to run the utests/dtests (for sanity sake).
[~spodxx@gmail.com] and [~iamaleksey]: if dtests/utests are happy, I'm thinking 3.0 and up can take this patch. Should we consider 2.2, as well? This is a bug, but not a critical one, so perhaps we should skip 2.2.
was (Author: jasobrown):
I'm +1 on the patch, and I'll setup a branch to run the utests/dtests (for sanity sake).
[~spodxx@gmail.com] and [~iamaleksey]: dtests/utests are happy, I'm thinking 3.0 and up can take this patch. Should we consider 2.2, as well? This is a bug, but not a critical one, so perhaps we should skip 2.2.
> Uncaught exceptions in Netty pipeline
> -------------------------------------
>
> Key: CASSANDRA-13649
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13649
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging, Testing
> Reporter: Stefan Podkowinski
> Assignee: Norman Maurer
> Labels: patch
> Attachments: 0001-CASSANDRA-13649-Ensure-all-exceptions-are-correctly-.patch, test_stdout.txt
>
>
> I've noticed some netty related errors in trunk in [some of the dtest results|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/106/#showFailuresLink]. Just want to make sure that we don't have to change anything related to the exception handling in our pipeline and that this isn't a netty issue. Actually if this causes flakiness but is otherwise harmless, we should do something about it, even if it's just on the dtest side.
> {noformat}
> WARN [epollEventLoopGroup-2-9] 2017-06-28 17:23:49,699 Slf4JLogger.java:151 - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
> io.netty.channel.unix.Errors$NativeIoException: syscall:read(...)() failed: Connection reset by peer
> at io.netty.channel.unix.FileDescriptor.readAddress(...)(Unknown Source) ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> {noformat}
> And again in another test:
> {noformat}
> WARN [epollEventLoopGroup-2-8] 2017-06-29 02:27:31,300 Slf4JLogger.java:151 - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
> io.netty.channel.unix.Errors$NativeIoException: syscall:read(...)() failed: Connection reset by peer
> at io.netty.channel.unix.FileDescriptor.readAddress(...)(Unknown Source) ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> {noformat}
> Edit:
> The {{io.netty.channel.unix.Errors$NativeIoException: syscall:read(...)() failed}} error also causes tests to fail for 3.0 and 3.11.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org