cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steinmaurer, Thomas" <>
Subject RE: Stable Cassandra 3.x version for production
Date Tue, 07 Nov 2017 13:47:04 GMT
Latest DSE is based on 3.11 (possibly due to CASSANDRA-12269, but just a guess).

For us (only), none of 3.0+/3.11+ qualifies for production to be honest, when you are familiar
with having 2.1 in production.

·         3.0 needs more hardware resources to handle the same load =>
Improved (close/back to 2.1 level) in 3.11

·         With 3.11.0 we are seeing the following memory leak (at least here, but possibly
nobody else out there, cause the ticket gets close to zero attention *g*):

·         From an operational perspective, the repair area got much more troublesome compared
to 2.1 when introducing incremental repairs being the default in 2.2+

We stay on 2.1 for now.

Just my opinion.


From: Herbert Fischer []
Sent: Dienstag, 07. November 2017 14:35
Subject: Re: Stable Cassandra 3.x version for production

I know that people usually prefers to use the 3.0.x branch because that's the one that is
underneath DSE.

I've never heard of anyone using Cassandra > 3.0.x on production.

On Tue, Nov 7, 2017 at 11:29 AM, shini gupta <<>>


Which version of Cassandra 3.x is stable and production-ready?


Herbert Fischer | Senior IT Architect
CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin


Amtsgericht Berlin-Charlottenburg | HRB 169537 B
Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202
The contents of this e-mail are intended for the named addressee only. It contains information
that may be confidential. Unless you are the named addressee or an authorized designee, you
may not copy or use it, or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN
91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria,
Freistädterstraße 313
View raw message