dra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Friday, June 21, 2013 5:40 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Updated sstable size for LCS, ran upgradesstables, file sizes didn&#
*user@cassandra.apache.org
> *Sent: *Friday, June 21, 2013 4:51:29 PM
> *Subject: *Re: Updated sstable size for LCS, ran upgradesstables, file
> sizes didn't change
>
>
> On Fri, Jun 21, 2013 at 4:40 PM, Andrew Bialecki
> wrote:
> > However when we run alter the column
>
ve a nodetool command to change the
> SSTable Size and trigger the rebuild of the SSTables.
>
> Thanks.
> -Wei
>
> --
> *From: *"Robert Coli"
> *To: *user@cassandra.apache.org
> *Sent: *Friday, June 21, 2013 4:51:29 PM
> *Subject
the rebuild of the SSTables.
Thanks.
-Wei
- Original Message -
From: "Robert Coli"
To: user@cassandra.apache.org
Sent: Friday, June 21, 2013 4:51:29 PM
Subject: Re: Updated sstable size for LCS, ran upgradesstables, file sizes
didn't change
On Fri, Jun 21,
On Fri, Jun 21, 2013 at 4:40 PM, Andrew Bialecki
wrote:
> However when we run alter the column
> family and then run "nodetool upgradesstables -a keyspace columnfamily," the
> files in the data directory have been re-written, but the file sizes are the
> same.
>
> Is this the expected behavior? If
We're potentially considering increasing the size of our sstables for some
column families from 10MB to something larger.
In test, we've been trying to verify that the sstable file sizes change and
then doing a bit of benchmarking. However when we run alter the column
family and then run "nodetool
