You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/10/07 14:32:00 UTC
[jira] [Comment Edited] (CASSANDRA-16518) Node restart during
joining sets protocol version to V3
[ https://issues.apache.org/jira/browse/CASSANDRA-16518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425598#comment-17425598 ]
Brandon Williams edited comment on CASSANDRA-16518 at 10/7/21, 2:31 PM:
------------------------------------------------------------------------
Your analysis looks spot on to me. I believe check from CASSANDRA-15193 is seeing the unknown version and capping the protocol. One possible way to solve this may be to get of preferred_ip altogether, an idea I've floated on CASSANDRA-16718, which is another problem regarding it. [~samt] wdyt?
was (Author: brandon.williams):
Your analysis looks spot on to me. I believe check from CASSANDRA-15193 is seeing the unknown version and capping the protocol. One possible way to solve this may be to get of preferred_ip altogether, an idea I've floated on CASSANDRA-16718, which is another problem regarding it.
> Node restart during joining sets protocol version to V3
> -------------------------------------------------------
>
> Key: CASSANDRA-16518
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16518
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Joseph Clay
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 3.11.x
>
>
> While joining nodes to a cluster, an old node crashed. The old node was recovered however clients (datastax java) refused to connect to it.
> The driver error:
> {noformat}
> Detected added or restarted Cassandra host /<ip>:<port> but ignoring it since it does not support the version V4 of the native protocol which is currently in use.{noformat}
> In the recovered node cassandra logs:
> {noformat}
> INFO o.a.c.transport.ConfiguredLimit Detected peers which do not fully support protocol V4. Capping max negotiable version to V3{noformat}
> I confirmed that ALL the nodes in the cluster, joining or otherwise, were apache-cassandra-3.11.6 so that error message was rather confusing.
> Eventually after digging through the code we got to the bottom of the issue:
> https://issues.apache.org/jira/browse/CASSANDRA-15193 adds a check for node version, which reverts the protocol version to V3 if any peer fails the version check. Joining nodes have NULL for their version in the peers table, which fails the version check.
>
--
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