Hi there,
I am using 2.0.10 and my Cassandra node has 6 disks and I configured 6 data
directories in cassandra.yaml. But the data was not evenly stored on these
6 disks:
disk1 67% used
> disk2 100% used
> disk3 100% used
> disk4 76% used
> disk5 69% used
> disk6 81% used
>
>
So:
1.
What compaction strategy are you using?
>venkat
From: Yatong Zhang
Sent: Saturday, November 1, 2014 12:32 PM
To: user@cassandra.apache.org
Hi there,
I am using 2.0.10 and my Cassandra node has 6 disks and I configured 6 data
directories in cassandra.yaml. But the data
We've been commissioning some new nodes on a 2.0.10 community edition
cluster, and we're seeing streams that look like they're shipping way more
data than they ought for individual files during bootstrap.
/var/lib/cassandra/data/x/y/x-y-jb-11748-Data.db
3756423/3715409 bytes(101%)
leveled compaction
On Sat, Nov 1, 2014 at 5:53 PM, venkat sam wrote:
> What compaction strategy are you using?
>
> >venkat
> *From:* Yatong Zhang
> *Sent:* Saturday, November 1, 2014 12:32 PM
> *To:* user@cassandra.apache.org
>
> Hi there,
>
> I am using 2.0.10 and my Cassandra nod
Hi,
I recently ran a migration where I modified (essentially, deleted and inserted)
a large number of clustering keys. This obviously created a lot of tombstones
and now I am receiving warnings in my logs that number of tombstones are above
a certain threshold when I query all rows for a certa
