[
https://issues.apache.org/jira/browse/CASSANDRA-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314264#comment-14314264
]
Ron Kuris commented on CASSANDRA-8768:
--------------------------------------
This works fine, though, when going the other direction already (that is, a 2.1
seed and a 2.0 node bootstrapping). It also works fine if the node happens to
be in the cached list; it only fails when the node doesn't have the cached
entry for this IP.
The schema was fetched just fine from the 2.0 nodes. The code drops down to the
older version, and there is a lot of code to support this already due to the
reverse case working fine.
Even if you decide this should not be fixed, the error message is terrible, and
requires the user to turn it up to debug before getting a possible clue as to
the problem. I'd suggest at least:
{code}logger.warn("Seed gossip version is {}; will not connect with that
version", maxTargetVersion);
> Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-8768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8768
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Ron Kuris
> Fix For: 2.1.3
>
> Attachments: gossip-with-2.0-patch.txt
>
>
> If you spin up a Cassandra 2.0 cluster with some seeds, and then attempt to
> attach a Cassandra 2.1 node to it, you get the following message:
> {code}OutboundTcpConnection.java:429 - Handshaking version with
> /10.24.0.10{code}
> Turning on debug, you get a few additional messages:
> {code}DEBUG [WRITE-/(ip)] MessagingService.java:789 - Setting version 7 for
> /10.24.0.10
> DEBUG [WRITE-/(ip)] OutboundTcpConnection.java:369 - Target max version is 7;
> will reconnect with that version{code}
> However, the code never reconnects. See the comments as to why.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
