There’s a tweak to TWCS in 3.11.1 that lets data expire faster, but I wouldn’t call it unstable in any version I’ve ever used it with. I’ve deployed it on 2.0, 2.1, 2.2 [1], and used it in every version of C* that we’ve shipped it, and have never had an issue.
I would put 3.11.1 in prod over 3.0, there’s a number of performance improvements and a few nice features that make it worth it. Off the top of my head, off heap memtables, a nice LIMIT optimization, and more flexible allow filtering options are all nice. [1] http://thelastpickle.com/blog/2017/01/10/twcs-part2.html <http://thelastpickle.com/blog/2017/01/10/twcs-part2.html> > On Jan 7, 2018, at 2:33 AM, shalom sagges <shalomsag...@gmail.com> wrote: > > Thanks Guys! > > Sorry for the late reply. > I'm interested in TWCS where I understand is more stable in 3.11.1 than in > 3.0.15, tombstone compaction and slow logs. > > I don't plan to use MVs and SASI in the near future, as I understand are not > Production ready. > > Is it okay to use the above features? > > > > > > On Thu, Jan 4, 2018 at 1:07 AM, Mick Semb Wever <m...@thelastpickle.com > <mailto:m...@thelastpickle.com>> wrote: > > > I want to upgrade from 2.x to 3.x. > > I can definitely use the features in 3.11.1 but it's not a must. > So my question is, is 3.11.1 stable and suitable for Production compared to > 3.0.15? > > > Use 3.11.1 and don't use any 3.0.x or 3.x features. > 3.11.1 is effectively three sequential patch releases, and the tick-tock > releases offered a number of superior fixes and performance improvements over > what was done in 3.0.x. > > Introduce the use of new features later on, one at a time, after thorough > testing and staging. > > regards, > Mick >
