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

Brad Schoening edited comment on CASSANDRA-16940 at 9/10/21, 3:36 PM:
----------------------------------------------------------------------

I agree its odd.  During the time we were seeing this error, our code was able 
to connect using the Java driver with protocol v3 explicitly defined in the 
code and CQLSH 5.0.1 with v3 and v4 protocol – some nodes would negotiate down 
to v3, most would use v4.

our logs also had these info messages:

2021-09-08 19:46:40,634 [INFO ] [main] cluster_id=29 ip_address=169.99.224.209  
SystemKeyspace.java:891 - No version string found for /169.94.131.176

2021-09-08 19:46:40,634 [INFO ] [main] cluster_id=29 ip_address=169.99.224.209  
SystemKeyspace.java:891 - No version string found for /169.94.131.174

2021-09-08 19:46:40,635 [INFO ] [main] cluster_id=29 ip_address=169.99.224.209  
ConfiguredLimit.java:108 - Detected peers which do not fully support protocol 
V4. Capping max negotiable version to V3


was (Author: bschoeni):
I agree its odd.  During the time we were seeing this error, our code was able 
to connect using the Java driver with protocol v3 explicitly defined in the 
code and CQLSH 5.0 with v3 and v4 protocol – some nodes would negotiate down to 
v3, most would use v4.

our logs also had these info messages:

2021-09-08 19:46:40,634 [INFO ] [main] cluster_id=29 ip_address=169.99.224.209  
SystemKeyspace.java:891 - No version string found for /169.94.131.176

2021-09-08 19:46:40,634 [INFO ] [main] cluster_id=29 ip_address=169.99.224.209  
SystemKeyspace.java:891 - No version string found for /169.94.131.174

2021-09-08 19:46:40,635 [INFO ] [main] cluster_id=29 ip_address=169.99.224.209  
ConfiguredLimit.java:108 - Detected peers which do not fully support protocol 
V4. Capping max negotiable version to V3

> Confusing ProtocolException msg Invalid or unsupported protocol version (4)
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16940
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16940
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Messaging/Client
>            Reporter: Brad Schoening
>            Priority: Normal
>
> The following warning was seen frequently after upgrading from 3.0.15 to 
> 3.11.11 in the cassandra.log:
> {noformat}
> ProtocolException: Invalid or unsupported protocol version (4); supported 
> versions are (3/v3, 4/v4, 5/v5-beta){noformat}
> It is at best unclear, or maybe a bug in the code throwing this exception 
> stating version '4' not supported but 4/v4 is.
> from org/apache/cassandra/transport/ProtocolVersion.java
> public static String invalidVersionMessage(int version)
> { return String.format("Invalid or unsupported protocol version (%d); 
> supported versions are (%s)", version, String.join(", ", 
> ProtocolVersion.supportedVersions())); }
> We later found invalid IP addresses in the system.peers table and once 
> removed, this exception went away.



--
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

Reply via email to