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

Vivekanand Koya edited comment on CASSANDRA-20984 at 11/4/25 4:16 AM:
----------------------------------------------------------------------

Since we already check the outcomes we don't need to perform an instanceof 
check on MessagingSuccess in the code path (OutboundConnection.java). Here is a 
patch for 4.1: 
[https://github.com/vivekkoya/cassandra/tree/cassandra-4.1|https://github.com/vivekkoya/cassandra/tree/cassandra-4.1.]


was (Author: JIRAUSER307377):
Since we already check the outcomes we don't need to perform an instanceof 
check on MessagingSuccess in the code path (OutboundConnection.java). Here is a 
patch for 4.1: [https://github.com/vivekkoya/cassandra/tree/cassandra-4.1.] 

> Fix java.lang.ClassCastException: Streaming Incompatible versions
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-20984
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20984
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Consistency/Bootstrap and Decommission, 
> Consistency/Streaming
>            Reporter: Vivekanand Koya
>            Assignee: Vivekanand Koya
>            Priority: Normal
>             Fix For: 4.1.x, 5.0.x, 5.x
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> On version mismatch or protocol incompatibility between the two communicating 
> nodes, cassandra server does not handle the errors correctly. There is no 
> proper error handling when ClassCastException occurs, since it is not 
> consistently reproducible. 
> In 
> [https://lists.apache.org/thread/ykkwhjdpgyqzw5xtol4v5ysz664bxxl3.,|https://lists.apache.org/thread/ykkwhjdpgyqzw5xtol4v5ysz664bxxl3.]
>  the "Stream failed" message points to a streaming operation, which is used 
> for processes like node repairs or adding new nodes (bootstrapping). I found 
> a similar Jira that was already raised - 
> https://issues.apache.org/jira/browse/CASSANDRA-19218.  Not sure what to do 
> with this JIRA. Looks like a duplicate.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to