Nice work guys. Just to confirm, if you upgrade from, 2.2.x say, directly to 3.3, you will *not* need to run upgradesstables, right? It seems pretty clear that the answer is no but I just wanted to make sure. Only needed if you got from a 3.x version?
Thank you. Sent from my iPhone > On 9 Feb 2016, at 19:06, Jake Luciani <jak...@gmail.com> wrote: > > No problem. Run it after you upgrade. > >> On Tue, Feb 9, 2016 at 2:01 PM, Will Hayworth <whaywo...@atlassian.com> >> wrote: >> Pardon my ignorance, Jake--should we run upgradesstables -a after or before >> we install 3.3? >> >> Thanks! :) >> >> ___________________________________________________________ >> Will Hayworth >> Developer, Engagement Engine >> Atlassian >> >> My pronoun is "they". >> >> >> >>> On Tue, Feb 9, 2016 at 10:50 AM, Jake Luciani <j...@apache.org> wrote: >>> The Cassandra team is pleased to announce the release of Apache Cassandra >>> version 3.3. >>> >>> This release contains a critical bug in 3.0 series[4]. If you have >>> installed version >= 3.0 >>> you will need to run 'nodetool upgradesstables -a' on all nodes to receive >>> the fix. >>> >>> Apache Cassandra is a fully distributed database. It is the right choice >>> when you need scalability and high availability without compromising >>> performance. >>> >>> http://cassandra.apache.org/ >>> >>> Downloads of source and binary distributions are listed in our download >>> section: >>> >>> http://cassandra.apache.org/download/ >>> >>> This version is a bug fix release[1] on the 3.3 series. As always, please >>> pay >>> attention to the release notes[2] and Let us know[3] if you were to >>> encounter >>> any problem. >>> >>> Enjoy! >>> >>> [1]: http://goo.gl/V2lsST (CHANGES.txt) >>> [2]: http://goo.gl/5UBlNl (NEWS.txt) >>> [3]: https://issues.apache.org/jira/browse/CASSANDRA >>> [4]: https://issues.apache.org/jira/browse/CASSANDRA-11102 > > > > -- > http://twitter.com/tjake
