[ https://issues.apache.org/jira/browse/CASSANDRA-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412861#comment-17412861 ]
Brandon Williams commented on CASSANDRA-16940: ---------------------------------------------- Hmm, nothing really makes sense on the surface here. Version 4 is obviously supported, and I don't see anything in the code here that would care about the peers table. [~samt] can you look? > 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.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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org