Good: doesn't OOM on smallish machines, can use defaults for almost all params w good results.
Bad: watch the list like a hawk to avoid problems others have, be aware of bug fixes, workarounds, and Jira issues. ml On Thu, Jan 9, 2014 at 12:58 PM, Bruce Durling <b...@otfrom.com> wrote: > So, what are you getting from 2.0 if you aren't using the new > features? Why not stick with 1.2.x? > > cheers, > Bruce > > On Thu, Jan 9, 2014 at 12:37 PM, Laing, Michael > <michael.la...@nytimes.com> wrote: > > I would like to +1 Jan. > > > > We are using C* 2.0 and have just gone into production directly > supporting > > the latest revision of www.nytimes.com. > > > > I avoid new features unless I really need them; we are prepared to read > code > > and make fixes ourselves if necessary, but it has not been. > > > > Best regards, > > > > Michael > > > > > > On Thu, Jan 9, 2014 at 7:04 AM, Jan Algermissen < > jan.algermis...@nordsc.com> > > wrote: > >> > >> > >> On 09.01.2014, at 03:36, Sanjeeth Kumar <sanje...@exotel.in> wrote: > >> > >> > Hi all, > >> > What is the latest stable version of cassandra you have in > production > >> > ? We are migrating a large chunk of our mysql database to cassandra. > I see a > >> > lot of discussions regarding 1.* versions, but I have not seen / > could not > >> > find discussions regarding using 2.* versions in production. Any > suggestions > >> > for the version based on your experience? > >> > > >> > >> I came to C* with 2.0 and have it up an running since about August. I > have > >> a production environment but can live with occasional problems. I could > even > >> setup the whole 3-node cluster from scratch without being killed :-) > >> > >> So I am happy with 2.0 having a short history of production use. > >> > >> What I noticed or saw on the list is that newer features (auto-paging, > CAS > >> support) seem to make it into the production releases in a > non-production > >> state. > >> > >> It appears this is generally accepted practice in the community - and > >> honestly, I would not really know how to thoroughly test such features > >> without handing them to the community to run them. So I do not think > the C* > >> crew is to blame, really. > >> > >> I have not had any issues with C* 2.0 when steering clear of these > >> features (e.g. manually disable paging when working with ranges and do > it > >> yourself). > >> > >> Jan > >> > >> > >> > >> > - Sanjeeth > >> > > > > > > -- > @otfrom | CTO & co-founder @MastodonC | mastodonc.com > See recent coverage of us in the Economist http://econ.st/WeTd2i and > the Financial Times http://on.ft.com/T154BA >
