cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien Anguenot <jul...@anguenot.org>
Subject Re: Cassandra stable version for production
Date Thu, 21 Jul 2016 08:34:38 GMT
Yes, we have been running 3.0.x for a while and we consider it mostly stable now.  Though,
we did not have to bootstrap new nodes / new DCs since running 3.0.x so I cannot speak about
that part.

In addition, DSE 5 is now running off 3.0.x which will definitely bring a lot of bug fixes
from Datastax production customers.

The only real issue we, and others, experienced while migrating to 3.0.x, is that one: 
   
   https://issues.apache.org/jira/browse/CASSANDRA-11887 <https://issues.apache.org/jira/browse/CASSANDRA-11887>

Tyler seems to think this issue might be related to that one that got fixed in upcoming 3.0.9:

   https://issues.apache.org/jira/browse/CASSANDRA-12144 <https://issues.apache.org/jira/browse/CASSANDRA-12144>

I agree with Jon about not putting Tick Tock release in production as it would definitely
require some major involvements to test and report issues every month. I know I would not
do it unless working on some non production projects that would require bleeding edge features.

Although, the tick tock release has advantages regarding new feature availability and new
feature short term stability I still believe a long term stable branch like 3.0.x is necessary
for most users. 

IMHO, considering the amount of questions asking what Cassandra version is ready for production,
that long term stable release should be the one listed as stable on http://cassandra.apache.org/
<http://cassandra.apache.org/> to avoid confusion.

Personally hoping both release models (tick tock and long term stable release) will still
co-exist after September.

   J. 

--
Julien Anguenot (@anguenot)

> On Jul 21, 2016, at 1:41 AM, Jonathan Haddad <jon@jonhaddad.com> wrote:
> 
> If I were starting a new project today, I'd go with 3.0.  It's gotten over half a year
of bug fixes.  
> 
> I personally would have a hard time putting a tick tock release into production, as you're
either getting new features or putting a version in which won't receive any further bug fixes,
so unless you're ready to dive into code or backport patches (or upgrade every month thereafter
to get bugfixes in addition to new features) 3.0 is probably your best bet.
> 
> Julien Anguenot talks a little bit about migrating his cluster to 3.0 here: http://planetcassandra.org/blog/this-week-in-cassandra-3-0-in-the-wild-5132016/
<http://planetcassandra.org/blog/this-week-in-cassandra-3-0-in-the-wild-5132016/>
> On Wed, Jul 20, 2016 at 4:33 PM Farzad Panahi <farzad.panahi@gmail.com <mailto:farzad.panahi@gmail.com>>
wrote:
> Hi, 
> 
> I am new to Cassandra and a bit confused about how versioning works here.
> 
> I have recently started working on Cassandra clusters. I want to create a Cassandra cluster
and make it ready for production but I am not sure which version is the right one. Some people
mention that the most stable version is 2.2 but when I look at Cassandra's download page it
says that ver 2.2 will be supported till November 2016 which does not look like a good candidate
for a new cluster.
> 
> So is the tick-tock release 3.7 stable enough for production or should I go with 3.0
or 2.2? Which one is the most robust and reliable one for production?
> 
> I appreciate if the community can share their thoughts.
> 
> Cheers
> 
> Farzad


Mime
View raw message