You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2022/03/01 17:26: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=17499664#comment-17499664 ]
Stefan Miklosovic edited comment on CASSANDRA-16518 at 3/1/22, 5:25 PM:
------------------------------------------------------------------------
I've already tested this as well my colleagues and they are saying it just works as expected. Given how complex the test is going to be, I am admitting I am quite hesitant to spend too much time on this. Additioanlly, I am not completely sure what test I should write, in-jvm dtest or python one? There is a lot of moving parts here and I am afraid I am going to introduce another flaky eventually.
Or maybe I could narrow down the scope of the test to test just stuff around ConfigLimit? What is your opinion on the scope the test should cover here?
was (Author: smiklosovic):
I've already tested this as well my colleagues and they are saying it just works as expected. Given how complex the test is going to be, I am admitting I am quite hesitant to spend too much time on this. Additioanlly, I am not completely sure what test I should write, in-jvm dtest or python one? There is a lot of moving parts here and I am afraid I am going to introduce another flaky eventually.
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org