How did that typo happen...
Of course I talked too soon.I saw a corrupted commitlog some days back after killing cassandra and I just came across a committed hints file after a cluster restart for some config changes :(Will look into that.Otherwise, not defaults, but close.The dataset is fed from scratch so yes, memtable_total_space is there.Some option tuning here and there and a few extra GC options and a relatively large patch which makes more compact serialization (this may help a bit...)Most of the tuning dates back to cassandra 0.6/0.7. It could be an interesting experiment to see if things got worse without them on 0.8.Hopefully I can submit the serialization patch soon.Regards,TerjeOn Mon, Jun 6, 2011 at 9:12 PM, Jonathan Ellis <email@example.com> wrote:
Has this been running w/ default settings (i.e. relying on the new
memtable_total_space_in_mb) or was this an upgrade from 0.7 (or
otherwise had the per-CF memtable settings applied?)
On Mon, Jun 6, 2011 at 12:00 AM, Terje Marthinussen
> 0.8 under load may turn out to be more stable and well behaving than any
> release so far
> Been doing a few test runs stuffing more than 1 billion records into a 12
> node cluster and thing looks better than ever.
> VM's stable and nice at 11GB. No data corruptions, dead nodes, full GC's or
> any of the other trouble that plagued early 0.7 releases.
> Still have to test more nasty stuff like rebalancing or recovering failed
> nodes, but so far I would recommend anyone to consider 0.8 over 0.7.x if
> setting up a new system
> On Fri, Jun 3, 2011 at 5:25 PM, Stephen Connolly
> <firstname.lastname@example.org> wrote:
>> Great work!
>> As the release of artifacts to Maven Central is now part of the
>> release process, the artifacts are all available from Maven Central
>> already (for people who use Maven/ANT+Ivy/Gradle/Buildr/etc)
>> On 3 June 2011 00:36, Eric Evans <email@example.com> wrote:
>> > I am very pleased to announce the official release of Cassandra 0.8.0.
>> > If you haven't been paying attention to this release, this is your last
>> > chance, because by this time tomorrow all your friends are going to be
>> > raving, and you don't want to look silly.
>> > So why am I resorting to hyperbole? Well, for one because this is the
>> > release that debuts the Cassandra Query Language (CQL). In one fell
>> > swoop Cassandra has become more than NoSQL, it's MoSQL.
>> > Cassandra also has distributed counters now. With counters, you can
>> > count stuff, and counting stuff rocks.
>> > A kickass use-case for Cassandra is spanning data-centers for
>> > fault-tolerance and locality, but doing so has always meant sending data
>> > in the clear, or tunneling over a VPN. New for 0.8.0, encryption of
>> > intranode traffic.
>> > If you're not motivated to go upgrade your clusters right now, you're
>> > either not easily impressed, or you're very lazy. If it's the latter,
>> > would it help knowing that rolling upgrades between releases is now
>> > supported? Yeah. You can upgrade your 0.7 cluster to 0.8 without
>> > shutting it down.
>> > You see what I mean? Then go read the release notes to learn about
>> > the full range of awesomeness, then grab a copy and become a
>> > (fashionably )early adopter.
>> > Drivers for CQL are available in Python, Java, and Node.js.
>> > As usual, a Debian package is available from the project's APT
>> > repository.
>> > Enjoy!
>> > : http://goo.gl/CrJqJ (NEWS.txt)
>> > : http://cassandra.debian.org/download
>> > : http://www.apache.org/dist/cassandra/drivers
>> > : https://github.com/racker/node-cassandra-client
>> > : http://wiki.apache.org/cassandra/DebianPackaging
>> > --
>> > Eric Evans
>> > firstname.lastname@example.org
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support