[ https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380322#comment-17380322 ]
Berenguer Blasi commented on CASSANDRA-16677: --------------------------------------------- A similar alternative would be to mark it flaky which I am very tempted of. The problem I have with these solutions is that I can't assure those exceptions being benign. So painting a GA green by cosmetics rather than addressing the problem is sthg I hard -1 to myself lol... Why do we access a channel after a close? Who closes it? etc I just need to take a break from this and when the next gap comes along get netty's code, put extra logging all around and see who is closing that connection. My 2tcs. > Fix flaky ConnectionTest > ------------------------ > > Key: CASSANDRA-16677 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16677 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode > Reporter: Brandon Williams > Priority: Normal > Fix For: 4.0, 4.0-rc > > > https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/ > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069 > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065 -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org