So after CASSANDRA-579, anti compaction won't be done on the source node, and we can use more than 50% of the disk space if we use multiple column families?
Thanks, Sean On Wed, May 26, 2010 at 10:01 AM, Stu Hood <stu.h...@rackspace.com> wrote: > See https://issues.apache.org/jira/browse/CASSANDRA-579 for some > background here: I was just about to start working on this one, but it won't > make it in until 0.7. > > > -----Original Message----- > From: "Sean Bridges" <sean.brid...@gmail.com> > Sent: Wednesday, May 26, 2010 11:50am > To: user@cassandra.apache.org > Subject: using more than 50% of disk space > > We're investigating Cassandra, and we are looking for a way to get > Cassandra > use more than 50% of it's data disks. Is this possible? > > For major compactions, it looks like we can use more than 50% of the disk > if > we use multiple similarly sized column families. If we had 10 column > families of the same size, we could use 90% of the disk, since a major > compaction would only need as much free space as the largest column family > (in reality we would use less). Is that right? > > For bootstrapping new nodes, it looks like adding a new node will require > that an existing node does anti-compaction. This anti-compaction could > take > nearly 50% of the disk. Is there a way around this? > > Is there anything else that would prevent us from using more than 50% of > the > data disk. > > Thanks, > > Sean > > >
