RE: Cassandra 2.x Stability

On the cassandra web itself. http://cassandra.apache.org/download/ From: James Rothering [mailto:jrother...@codojo.me] Sent: 07 December 2016 00:50 To: user@cassandra.apache.org Subject: Re: Cassandra 2.x Stability Is there an official notification of these EOL dates somewhere? On Wed, Nov 30

Re: Cassandra 2.x Stability

Is there an official notification of these EOL dates somewhere? On Wed, Nov 30, 2016 at 4:38 AM, kurt Greaves wrote: > Latest release in 2.2. 2.1 is borderline EOL and from my experience 2.2 is > quite stable and has some handy bugfixes that didn't actually make it into >

Re: Cassandra 2.x Stability

No worries. I added some patches to these tickets after having tested them yesterday with our production cluster. I think this will be a huge step for MV stability. Anybody welcome to post comments on them or give me a review: CASSANDRA-12888, CASSANDRA-12905, CASSANDRA-12984 Thanks folks!

Re: Cassandra 2.x Stability

Ben, I just read through those two tickets. It's scarier than I thought. Thank you for all the investigations and comments. On Thu, Dec 1, 2016 at 10:31 AM, Benjamin Roth wrote: > A little experience report on MVs: > > We use them in production (3.10-trunk) and they

Re: Cassandra 2.x Stability

A little experience report on MVs: We use them in production (3.10-trunk) and they work really well on normal read/write operations but streaming operations (bootstrap, repair, rebuild, decommision) can kill your cluster and/or your nerves. We will stay with MVs as we need them and want them. I

Re: Cassandra 2.x Stability

I agree with everything you just said, Kai. I'd start a new project with 3.0.10. I'd stay away from MVs though. On Thu, Dec 1, 2016 at 10:19 AM Kai Wang wrote: > Just based on a few observations on this list. Not one week goes by > without people asking which release is the

Re: Cassandra 2.x Stability

Thanks a lot Kai! Shalom Sagges DBA T: +972-74-700-4035 We Create Meaningful Connections

Re: Cassandra 2.x Stability

Just based on a few observations on this list. Not one week goes by without people asking which release is the most stable on 3.x line. Folks at instaclustr also provide their own 3.x fork for stability issues. etc We developers already have enough to think about. I really don't feel like

Re: Cassandra 2.x Stability

Hey Kai, Thanks for the info. Can you please elaborate on the reasons you'd pick 2.2.6 over 3.0? Shalom Sagges DBA T: +972-74-700-4035 We Create Meaningful Connections

Re: Cassandra 2.x Stability

I have been running 2.2.6 in production. As of today I would still pick it over 3.x for production. On Nov 30, 2016 5:42 AM, "Shalom Sagges" wrote: > Hi Everyone, > > I'm about to upgrade our 2.0.14 version to a newer 2.x version. > At first I thought of upgrading to

Re: Cassandra 2.x Stability

You should also consider end of support term, as Cassandra page says: Apache Cassandra 2.2 is supported until November 2016. Apache Cassandra 2.1 is supported until November 2016 with critical fixes only So 2.1 actually don't get any fixes, even critical. Best regards, Vladimir Yudovin,

Re: Cassandra 2.x Stability

Latest release in 2.2. 2.1 is borderline EOL and from my experience 2.2 is quite stable and has some handy bugfixes that didn't actually make it into 2.1 On 30 November 2016 at 10:41, Shalom Sagges wrote: > Hi Everyone, > > I'm about to upgrade our 2.0.14 version to a

Cassandra 2.x Stability

Hi Everyone, I'm about to upgrade our 2.0.14 version to a newer 2.x version. At first I thought of upgrading to 2.2.8, but I'm not sure how stable it is, as I understand the 2.2 version was supposed to be a sort of beta version for 3.0 feature-wise, whereas 3.0 upgrade will mainly handle the