[
https://issues.apache.org/jira/browse/CASSANDRA-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543850#comment-13543850
]
Brandon Williams commented on CASSANDRA-5102:
---------------------------------------------
bq. hadn't we decided that we should not change the protocol version in a minor
version because it breaks streaming and we were only fine doing that for major
upgrades?
We had, but unfortunately it was the only way to fix what is hopefully the last
of our schema problems in 1.1. The impact from CASSANDRA-4880 is much worse
than having to upgrade all nodes before streaming.
bq. I wish some warning in the NEWS file for 1.1.7 had been added with
CASSANDRA-4880 to explain that streaming would be broken during pre-1.1.7 to
post-1.1.7 upgrades
Totally agree.
> upgrading from 1.1.7 to 1.2.0 caused upgraded nodes to only know about other
> 1.2.0 nodes
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-5102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5102
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Michael Kjellman
> Assignee: Brandon Williams
> Priority: Blocker
> Fix For: 1.2.1
>
> Attachments: 5102.txt
>
>
> I upgraded as I have since 0.86 and things didn't go very smoothly.
> I did a nodetool drain to my 1.1.7 node and changed my puppet config to use
> the new merged config. When it came back up (without any errors in the log) a
> nodetool ring only showed itself. I upgraded another node and sure enough now
> nodetool ring showed two nodes.
> I tried resetting the local schema. The upgraded node happily grabbed the
> schema again but still only 1.2 nodes were visible in the ring to any
> upgraded nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
