If you don't want your APT-sourced packages to upgrade automatically, I suggest
pinning the package.
The apt_preferences(5) man page tells you how to do this.
The gist is to add the following lines:
Package: cassandra
Pin: version 0.6.13
Pin-Priority: 1100
(setting the version to the one
We have Collectd (http://www.collectd.org/) monitoring Cassandra via its
Java/JMX plugin. Collectd feeds data to a central Graphite/Carbon
(http://graphite.wikidot.com/start) instance via
https://github.com/indygreg/collectd-carbon . With Graphite, you can
effortlessly utilize the web UI (or HT
> With the large new-gen, you were actually seeing fallbacks to full GC?
> You weren't just still experiencing problems because at 10 gig, the new-gen
> will be so slow to compact to effectively be similar to a full gc in terms of
> affecting latency?
Yes, we were seeing fallbacks to full GC with
nything useful from me anytime soon.
I hope this information helps. If you need anything else, just ask, and I'll
see what I can do.
Gregory Szorc
gregory.sz...@xobni.com
> -Original Message-
> From: sc...@scode.org [mailto:sc...@scode.org] On Behalf Of Peter
> Schuller
rote:
I worked on that ticket, will try to chase it up.
Aaron
On 15/02/2011, at 2:01 PM, Gregory Szorc
mailto:gregory.sz...@gmail.com>> wrote:
The latest official 0.6.x releases, 0.6.10 and 0.6.11, have a very serious
bug/regression when performing some quorum reads (CASSANDRA-2081), which
he web site) is swift and maximizes the potential for data integrity
and availability.
If there is anything I can do to help the process, I'd gladly give some of
my time to help the overall community.
Gregory Szorc
gregory.sz...@gmail.com
