> 1) Am I reading things correctly?
Yes.
If you do a read/slice by name and more than min compaction level nodes where
read the data is re-written so that the next read uses fewer SSTables.
> 2) What is really happening here? Essentially minor compactions can occur
> between 4 and 32 memtable
Thanks for the hint. But we gave up on trying to upgrade with no data loss,
since it was not required at this point.
On Wed, Dec 12, 2012 at 5:03 PM, aaron morton wrote:
> *in-vm cassandra*
>
> Embedded ?
>
> The location of the SSTables has changed in 1.1, they are know in
> /var/lib/cassandr
> periodically trimming the row by by deleting the oldest columns, the deleted
> columns won't get cleaned up until all fragments of the row exist in a single
> sstable and that sstable undergoes a compaction?
Nope.
They are purged when all of the fragments of the row exist in the same SSTabels
Brian- did you ever file any bugs with the issues you experienced?
On Dec 16, 2012, at 6:35 AM, "Peter Lin" wrote:
> I'm using
>
> Java(TM) SE Runtime Environment (build 1.7.0_07-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
>
>
>
> On Sun, Dec 16, 2012 at 4:54 AM, Sy
I'm using
Java(TM) SE Runtime Environment (build 1.7.0_07-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
On Sun, Dec 16, 2012 at 4:54 AM, Sylvain Lebresne wrote:
> On Sat, Dec 15, 2012 at 7:12 PM, Michael Kjellman
> wrote:
>>
>> What "issues" have you ran into? Actually c
On Sat, Dec 15, 2012 at 7:12 PM, Michael Kjellman
wrote:
> What "issues" have you ran into? Actually curious because we push 1.1.5-7
> really hard and have no issues whatsoever.
>
>
A related question is "which which version of java 7 did you try"? The
first releases of java 7 were apparently famo
