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

Berenguer Blasi edited comment on CASSANDRA-16677 at 6/4/21, 9:15 AM:
----------------------------------------------------------------------

I am really confused. After the recent sudden protocol/connection flakies I 
can't run Connection test locally anymore at all without failing with a million 
such messages. I have gone back as far as 4.0-beta4 and it still fails:

{noformat}
ant test -Dtest.name=ConnectionTest

[junit-timeout] WARN  
[Messaging-OUT-/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES] 2021-06-04 
10:42:00,776 OutboundConnection.java:488 - 
/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES-8fa2dfba dropping message of 
type _TEST_1 due to error
[junit-timeout] org.apache.cassandra.net.InvalidSerializedSizeException: 
Invalid serialized size; expected 30, actual size at least 29, for verb _TEST_1
[junit-timeout]         at 
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.doRun(OutboundConnection.java:984)
[junit-timeout]         at 
org.apache.cassandra.net.OutboundConnection$Delivery.run(OutboundConnection.java:687)
[junit-timeout]         at 
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.run(OutboundConnection.java:955)
[junit-timeout]         at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[junit-timeout]         at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit-timeout]         at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout]         at java.lang.Thread.run(Thread.java:748)
{noformat}



was (Author: bereng):
I am really confused. After the recent sudden protocol/connection flakies I 
can't run Connection test locally anymore at all without failing with a million 
such messages:

{noformat}
ant test -Dtest.name=ConnectionTest

[junit-timeout] WARN  
[Messaging-OUT-/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES] 2021-06-04 
10:42:00,776 OutboundConnection.java:488 - 
/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES-8fa2dfba dropping message of 
type _TEST_1 due to error
[junit-timeout] org.apache.cassandra.net.InvalidSerializedSizeException: 
Invalid serialized size; expected 30, actual size at least 29, for verb _TEST_1
[junit-timeout]         at 
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.doRun(OutboundConnection.java:984)
[junit-timeout]         at 
org.apache.cassandra.net.OutboundConnection$Delivery.run(OutboundConnection.java:687)
[junit-timeout]         at 
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.run(OutboundConnection.java:955)
[junit-timeout]         at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[junit-timeout]         at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit-timeout]         at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout]         at java.lang.Thread.run(Thread.java:748)
{noformat}


> Fix flaky ConnectionTest.testMessageDeliveryOnReconnect
> -------------------------------------------------------
>
>                 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to