[
https://issues.apache.org/jira/browse/CASSANDRA-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536804#comment-17536804
]
Jai Bheemsen Rao Dhanwada edited comment on CASSANDRA-16940 at 5/13/22 6:07 PM:
--------------------------------------------------------------------------------
I had a similar issue and when I started looking at code to see why it is
happening.
{code:java}
boolean enforceV3Cap = SystemKeyspace.loadPeerVersions()
.values()
.stream()
.anyMatch(v ->
v.compareTo(MIN_VERSION_FOR_V4) < 0);
{code}
Inspecting the system.peers table, one of the node in the cluster has a null
entry, which is causing the specific node to cap the max negotiable version to
V3.
{code:java}
> select peer, release_version from system.peers;
peer | release_version
--------------+----------------
10.41.128.35 | 3.11.9
10.41.128.228 | null
10.41.128.99 | 3.11.9
(3 rows)
{code}
However, I am not sure why there is a null entry in the peers table. Also I
checked the
{noformat}
nodetool status{noformat}
and
{noformat}
nodetool describecluster{noformat}
and I don't see this specific IP present. Not sure if there is a bug that is
causing this?
was (Author: jaid):
I had a similar issue and when I started looking at code to see why it is
happening.
```
boolean enforceV3Cap = SystemKeyspace.loadPeerVersions()
.values()
.stream()
.anyMatch(v ->
v.compareTo(MIN_VERSION_FOR_V4) < 0);
```
Inspecting the system.peers table, one of the node in the cluster has a null
entry, which is causing the specific node to cap the max negotiable version to
V3.
```
> select peer, release_version from system.peers;
peer | release_version
---------------+-----------------
10.41.128.35 | 3.11.9
10.41.128.228 | null
10.41.128.99 | 3.11.9
(3 rows)
```
However, I am not sure why there is a null entry in the peers table. Also I
checked the `nodetool status` and `nodetool describecluster` and I don't see
this specific IP present. Not sure if there is a bug that is causing this?
> 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.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
