ickle.com
On 6/03/2012, at 11:13 PM, Stefan Reek wrote:
Hi Aaron,
Thanks for the quick reply.
All our writes/deletes are done with CL.QUORUM.
Our reads are done with CL.ONE. Although the reads that confirmed the
old data were done with CL.QUORUM.
According to
https://svn.apache.org/viewvc/cas
anything suspicious
post examples.
Finally I would ensure CL QUROUM was been used.
Hope that helps.
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 6/03/2012, at 10:13 PM, Stefan Reek wrote:
Hi,
We were running a 3-node cluster of cassan
Hi,
We were running a 3-node cluster of cassandra 0.6.13 with RF=3.
After we added a fourth node, keeping RF=3, some old data appeared in
the database.
As far as I understand this can only happen if nodetool repair wasn't
run for more than GCGraceSeconds.
Our GCGraceSeconds is set to the defau
mean size: 0
On 02/28/2012 06:51 PM, Dan Retzlaff wrote:
Hi Stefan. Can you share the output of nodetool cfstats?
On Tue, Feb 28, 2012 at 1:50 AM, Stefan Reek <mailto:ste...@unitedgames.com>> wrote:
Hi All,
We are running a 3-node cluster with Cassandra 0.6.13.
We are in th
Hi All,
We are running a 3-node cluster with Cassandra 0.6.13.
We are in the process of upgrading to 1.x, but can't do so for a while
because we can't take the cluster offline.
Until now 0.6.13 has run without problems, but lately we are getting
some performance issues.
We are getting timeouts
I personally use Munin with the jmx2munin plugin. Works perfectly for me.
On 10/12/2011 06:35 PM, David McNelis wrote:
Brian,
Have you looked at Datastax OpsCenter? I think it would do a lot of
what you're looking for.
On Wed, Oct 12, 2011 at 11:27 AM, Brian Fleming
mailto:bigbrianflem...
10/06/2011 06:15 PM, Jonathan Ellis wrote:
On Thu, Oct 6, 2011 at 10:53 AM, Stefan Reek wrote:
We do have the commitlogs on separate devices, are there any other basics
that I could have forgotten, or
any parameters that are important for write performance?
1.0 write performance is some
On 10/06/2011 05:26 PM, Jonathan Ellis wrote:
On Thu, Oct 6, 2011 at 10:09 AM, Stefan Reek wrote:
I can see that during the times the writing gets slow there are ~3000
pending tasks, but they disappear quickly.
Your best bet is to make the write load more constant and less bursty
Hi guys,
We're currently testing an application against a very high load, which
runs against Cassandra 0.6.13 (I know, we just never got the time to
upgrade).
The nature of our app is that it will write to two different
SuperColumnFamilies in bursts, and to some other columnfamilies less
frequent
