On Mon, Jun 17, 2013 at 3:28 PM, Wei Zhu wrote:
> default value of 5MB is way too small in practice. Too many files in one
> directory is not a good thing. It's not clear what should be a good number.
> I have heard people are using 50MB, 75MB, even 100MB. Do your own test o
> find a "right" numb
Correction, the largest I heard is 256MB SSTable size.
- Original Message -
From: "Wei Zhu"
To: user@cassandra.apache.org
Sent: Sunday, June 16, 2013 10:28:25 PM
Subject: Re: Large number of files for Leveled Compaction
default value of 5MB is way too small in practice. Too many f
default value of 5MB is way too small in practice. Too many files in one
directory is not a good thing. It's not clear what should be a good number. I
have heard people are using 50MB, 75MB, even 100MB. Do your own test o find a
"right" number.
-Wei
- Original Message -
From: "Franc
On Mon, Jun 17, 2013 at 2:59 PM, Manoj Mainali wrote:
> Not in the case of LeveledCompaction. Only SizeTieredCompaction merges
> smaller sstables into large ones. With the LeveledCompaction, the sstables
> are always of fixed size but they are grouped into different levels.
>
> You can refer to th
Not in the case of LeveledCompaction. Only SizeTieredCompaction merges
smaller sstables into large ones. With the LeveledCompaction, the sstables
are always of fixed size but they are grouped into different levels.
You can refer to this page
http://www.datastax.com/dev/blog/leveled-compaction-in-a
On Mon, Jun 17, 2013 at 2:47 PM, Manoj Mainali wrote:
> With LeveledCompaction, each sstable size is fixed and is defined by
> sstable_size_in_mb in the compaction configuration of CF definition and
> default value is 5MB. In you case, you may have not defined your own value,
> that is why your ea
On Fri, Jun 7, 2013 at 2:44 PM, Franc Carter wrote:
>
> Hi,
>
> We are trialling Cassandra-1.2(.4) with Leveled compaction as it looks
> like it may be a win for us.
>
> The first step of testing was to push a fairly large slab of data into the
> Column Family - we did this much faster (> x100) th
With LeveledCompaction, each sstable size is fixed and is defined by
sstable_size_in_mb in the compaction configuration of CF definition and
default value is 5MB. In you case, you may have not defined your own value,
that is why your each sstable is 5MB. And if you dataset is huge, you will
see a l
in case you do not know yet, opscenter is sending certain data about
your cassandra instalation back to datastax.
This fact is not visibly presented to user, its same spyware crap like
EHCache.
I have a column family defined as:
create column family LSItemIdsByFieldValueIndex_Integer
with column_type = 'Standard'
and comparator =
'CompositeType(org.apache.cassandra.db.marshal.IntegerType,org.apache.cassandra.db.marshal.UTF8Type)'
and default_validation_class = 'UTF8Type'
and key
10 matches
Mail list logo
