I think it is an acceptable idea to build the latest code in cassandra-2.1 branch rather than waiting for official release because the older versions for 2.1.x indeed have some serious issues. At least I did this in our cluster and our troubles in 2.1.1 had been fixed.
2015-04-22 15:22 GMT+08:00 Nathan Bijnens <nat...@nathan.gs>: > We had some serious issues with 2.1.3: > - Bootstrapping a new node resulted in OOM > - Repair resulted in an OOM on several nodes > - When reading some parts of the data it caused cascading crashes on all > it's replica nodes. > > Downgrading to the 2.0.X branch didn't work because of some > incompatibilities, so we launched a new cluster and migrated all data. > > We will not be looking at 2.1 until we see some major resolved issues. > > IMHO if you don't need counters stick to the 2.0.X branch. DTCS is > available from 2.0.11. > > N. > > On Tue, Apr 21, 2015 at 11:50 PM Brian Sam-Bodden < > bsbod...@integrallis.com> wrote: > >> Robert, >> Can you elaborate more please? >> >> Cheers, >> Brian >> >> >> On Tuesday, April 21, 2015, Robert Coli <rc...@eventbrite.com> wrote: >> >>> On Tue, Apr 21, 2015 at 2:25 PM, Dikang Gu <dikan...@gmail.com> wrote: >>> >>>> We have some issues with streaming in 2.1.2. We find that there are a >>>> lot of patches in 2.1.5. Is it ready for upgrade? >>>> >>> >>> I personally would not run either version in production at this time, >>> but if forced, would prefer 2.1.5 over 2.1.2. >>> >>> =Rob >>> >>> >> >> >> -- >> Cheers, >> Brian >> http://www.integrallis.com >> >> -- Thanks, Phil Yang
