: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: sstable size change
alter table cookie_user_lookup with compaction={'sstable_size_in_mb': '256',
'class': 'LeveledCompactionStrategy'};
ionStrategy'};
>
> Thanks
>
> From: aaron morton
> Reply-To: "user@cassandra.apache.org"
> Date: Monday, July 29, 2013 4:02 AM
> To: "user@cassandra.apache.org"
> Subject: Re: sstable size change
>
>> I still would have expected my
<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: sstable size change
I still would have expected my original alter command to at least have thrown
an error. I assume I should open a bug for this?
Sounds like a good idea.
Please desc
ategy_options =
> {'sstable_size_in_mb':256};
>
>
> From: Keith Wright
> Reply-To: "user@cassandra.apache.org"
> Date: Thursday, July 25, 2013 9:14 AM
> To: "user@cassandra.apache.org" , Wei Zhu
>
> Subject: Re: sstable size change
>
"
mailto:user@cassandra.apache.org>>
Date: Thursday, July 25, 2013 9:14 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>, Wei Zhu
mailto:wz1...@yahoo.com>>
Subject: Re: sstable size change
Unfortun
eck_chance': '0.1',
'sstable_compression': 'LZ4Compressor'};
From: Wei Zhu mailto:wz1...@yahoo.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>, Wei
;user@cassandra.apache.org"
Sent: Wednesday, July 24, 2013 3:44 PM
Subject: Re: sstable size change
Hi all,
This morning I increased the SSTable size for one of my LCS via an alter
command and saw at least one compaction run (I did not trigger a compaction via
nodetool nor upgrad
gt;"
mailto:user@cassandra.apache.org>>
Date: Tuesday, July 23, 2013 3:04 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: sstable size change
"Will Cassandra force any newly compacted files to my new setti
"Will Cassandra force any newly compacted files to my new setting as
compactions are naturally triggered"
Yes. Let it compact and increase in size.
On Tue, Jul 23, 2013 at 9:38 AM, Robert Coli wrote:
> On Tue, Jul 23, 2013 at 6:48 AM, Keith Wright wrote:
>
>> Can you elaborate on what you mean
On Tue, Jul 23, 2013 at 6:48 AM, Keith Wright wrote:
> Can you elaborate on what you mean by "let it take its own course
> organically"? Will Cassandra force any newly compacted files to my new
> setting as compactions are naturally triggered?
>
You see, when two (or more!) SSTables love each o
pache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Monday, July 22, 2013 4:48 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: sstable size change
You can remove th
You can remove the json file and that will be treated as all sstables are
now in L0. Since you have lot of data, the compaction will take a very long
time. See the comment below directly from Cassandra code. If you chose to
do this, you might want to increase the rate of compaction by usual means.
My understanding is deleting the .json metadata file is the only way
currently. If you search the user list archives, there are folks who are
building tools to force compaction and rebuild sstables with the new size.
I believe there's been a bit of talk of potentially including those tools
as a pat
I don't think upgradesstables is enough, since it's more of a "change this file
to a new format but don't try to merge sstables and compact" -thing.
Deleting the .json -file is probably the only way, but someone more familiar
with cassandra LCS might be able to tell whether manually editing the
Hi all,
I know there has been several threads recently on this but I wanted to make
sure I got a clear answer: we are looking to increase our SSTable size for a
couple of our LCS tables as well as chunk size (to match the SSD block size).
The largest table is at 500 GB across 6 nodes (RF
15 matches
Mail list logo
