[ https://issues.apache.org/jira/browse/CASSANDRA-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497323#comment-17497323 ]
Srikanta Patra commented on CASSANDRA-13649: -------------------------------------------- Jason/Norman, we are using Cassandra ReleaseVersion: 3.11.11 We see the same issue. INFO [IndexSummaryManager:1] 2022-02-24 03:30:21,190 IndexSummaryRedistribution.java:78 - Redistributing index summaries WARN [epollEventLoopGroup-2-7] 2022-02-24 03:44:36,842 Message.java:785 - Unknown exception in client networking 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] And from the application side we see the below error: "errorMessage": "NoHostAvailableError: All host(s) tried for query failed. First host tried, 10.200.50.157:9042: DriverError: Connection timeout\n at Socket.connectTimedOut (/var/task/node_modules/cassandra-driver/lib/connection.js:205:19)\n at Object.onceWrapper (events.js:420:28)\n at Socket.emit (events.js:314:20)\n at Socket._onTimeout (net.js:483:8)\n at listOnTimeout (internal/timers.js:554:17)\n at processTimers (internal/timers.js:497:7) \{\n info: 'Cassandra Driver Error'\n}. See innerErrors.", Has it been fixed in the 3.11.11 version?? > Uncaught exceptions in Netty pipeline > ------------------------------------- > > Key: CASSANDRA-13649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13649 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Streaming and Messaging, Legacy/Testing > Reporter: Stefan Podkowinski > Assignee: Norman Maurer > Priority: Normal > Labels: patch > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x > > 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 (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org