Hi Jiri,
We do run multiple nodes with 2TB to 4TB of data and we will usually see GC
pressure when we create a lot of tombstones.
With Cassandra 2.0.x you would be able to see a log with the following pattern:
WARN [ReadStage:7] 2015-02-08 22:55:09,621 SliceQueryFilter.java (line 225)
Read 939 li
Hi everyone,
We are running some Cassandra clusters (Usually a cluster of 5 nodes with
replication factor of 3.) And at least once per day we do see some corruption
related to a specific sstable in system/hints. (We are using Cassandra version
1.2.16 on RHEL 6.5)
Here is an example of such ex
; Freelance Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 24/03/2013, at 3:42 AM, Francois Richard wrote:
>
> Hi,
>
> We currently run our Cassandra deployment with
> multiple independent clusters. The clusters are totally self con
hanks,
FR
--
_____
*Francois Richard *
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Saturday, July 23, 2011 5:05 PM
To: user@cassandra.apache.org
Subject: Re: do I need to add more nodes? minor compaction eat all IO
On Sat, Jul 23, 2011 at 4:16 PM, Francois Richard wrote:
> My understanding is that dur
This really depends on your disks setup.
When you run iostat under high load, do you see a high number of r/s but the
rMB/s is not so great?
I usually use:
iostat -x -m sdb sdc 1 to monitor situation like this.
In my case my disk setup is the following:
OS --> /sda
Cassandra CommitLogs --> /
debian/ubuntu we can fix them for ubuntu users.
I hope this helps!
On Sep 16, 2010, at 10:30 AM, Francois Richard wrote:
> Guys,
>
> I am trying to build a debian package in order to deploy Cassandra 0.6.5 on
> Ubuntu. I see that you have a ./debian directory in the sou
.
Thanks,
FR
Francois Richard