off topic for this discussion, and yea, we are in the midst of upgrading... 1.0.8 -> 1.0.12 then to 1.1.0.. then to the latest of 1.1.. then to 1.2. keep my finger cross for safe upgrading for such a big cluster... we hope that with cassandra moving some components off heap in 1.1 and 1.2, the cluster would perform better, at least i do not need to do the user defined compaction regulary.
thanks guys, jason On Tue, Mar 3, 2015 at 3:59 AM, <sean_r_dur...@homedepot.com> wrote: > In my experience, you do not want to stay on 1.1 very long. 1.08 was > very stable. 1.1 can get bad in a hurry. 1.2 (with many things moved > off-heap) is very much better. > > > > > > Sean Durity – Cassandra Admin, Big Data Team > > > > *From:* Robert Coli [mailto:rc...@eventbrite.com] > *Sent:* Monday, March 02, 2015 2:01 PM > *To:* user@cassandra.apache.org > *Subject:* Re: sstables remain after compaction > > > > On Sat, Feb 28, 2015 at 5:39 PM, Jason Wee <peich...@gmail.com> wrote: > > Hi Rob, sorry for the late response, festive season here. cassandra > version is 1.0.8 and thank you, I will read on the READ_STAGE threads. > > > > 1.0.8 is pretty seriously old in 2015. I would upgrade to at least 1.2.x > (via 1.1.x) ASAP. Your cluster will be much happier, in general. > > > > =Rob > > > > ------------------------------ > > The information in this Internet Email is confidential and may be legally > privileged. It is intended solely for the addressee. Access to this Email > by anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be > taken in reliance on it, is prohibited and may be unlawful. When addressed > to our clients any opinions or advice contained in this Email are subject > to the terms and conditions expressed in any applicable governing The Home > Depot terms of business or client engagement letter. The Home Depot > disclaims all responsibility and liability for the accuracy and content of > this attachment and for any damages or losses arising from any > inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other > items of a destructive nature, which may be contained in this attachment > and shall not be liable for direct, indirect, consequential or special > damages in connection with this e-mail message or its attachment. >
