[
https://issues.apache.org/jira/browse/CASSANDRA-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543706#comment-13543706
]
Sylvain Lebresne commented on CASSANDRA-5102:
---------------------------------------------
bq. if we ever do need to do another protocol bump in a minor, stable branch,
we're out of luck
I'm sorry I did not follow CASSANDRA_4880 more closely but 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?
Now I suppose what's done is done (though 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, and since it hadn't we should
probably document it now), but as long as protocol bump means breaking
streaming then I think we should maintain the rule "no bump in minor version"
(not that I wouldn't be against lifting the "protocol bump == break streaming"
limitation if possible but that's a different discussion).
> 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
