[
https://issues.apache.org/jira/browse/CASSANDRA-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578955#comment-13578955
]
Michael Kjellman commented on CASSANDRA-5104:
---------------------------------------------
if the versions are compat, by all means it should be allowed, but it is
equally as messy for the ned user in the middle of a upgrade currently. not
saying this is the best solution, but the current one is not the best imho.
> new nodes should not attempt to bootstrap and stream until entire cluster is
> on the same major version
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-5104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5104
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Michael Kjellman
> Assignee: Yuki Morishita
> Priority: Minor
> Fix For: 2.0
>
>
> current behavior for bootstrapping nodes is for an exception to be thrown
> while a node attempts to stream from another node that has not had
> upgradesstables run yet.
> A node should not attempt to bootstrap into the cluster until the entire
> cluster is on the same major version and upgradesstables has already been run
> on every node in the ring.
--
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
