cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5104) new nodes should not attempt to bootstrap and stream until entire cluster is on the same major version
Date Thu, 18 Jul 2013 18:30:51 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-5104:
--------------------------------------

    Fix Version/s:     (was: 2.0)
                   2.0.1
    
> 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.1
>
>
> 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

Mime
View raw message