You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brad Schoening (Jira)" <ji...@apache.org> on 2021/09/09 21:50:00 UTC

[jira] [Created] (CASSANDRA-16940) Confusing ProtocolException msg Invalid or unsupported protocol version (4)

Brad Schoening created CASSANDRA-16940:
------------------------------------------

             Summary: 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
            Reporter: Brad Schoening


The following warning was seen frequently after upgrading from 3.0.x 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.peer table and once removed, this exception went away.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org