[
https://issues.apache.org/jira/browse/CASSANDRA-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538131#comment-14538131
]
Ariel Weisberg commented on CASSANDRA-8768:
-------------------------------------------
[~iamaleksey], [~brandon.williams] is the unsupported nature of topology
changes during upgrade documented? I took a look at the upgrade doc and didn't
see it.
> 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
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.1.5
>
> 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)
