Dne 18.4.2012 16:22, Jonathan Ellis napsal(a):
It's not that simple, unless you have an append-only workload.
I have append only workload and probably most ppl using TTL too.
Per CF or per Row TTL would be very usefull for me also with our timeseries
data.
-Original Message-
From: Igor [mailto:i...@4friends.od.ua]
Sent: Wednesday, April 18, 2012 6:06 AM
To: user@cassandra.apache.org
Subject: Re: size tiered compaction - improvement
For my use case it would
It's not that simple, unless you have an append-only workload. (See
discussion on
https://issues.apache.org/jira/browse/CASSANDRA-3974.)
On Wed, Apr 18, 2012 at 4:57 AM, Radim Kolar wrote:
>
>> Any compaction pass over A will first convert the TTL data into
>> tombstones.
>>
>> Then, any subsequ
bject: Re: size tiered compaction - improvement
Any compaction pass over A will first convert the TTL data into tombstones.
Then, any subsequent pass that includes A *and all other sstables
containing rows with the same key* will drop the tombstones.
thats why i proposed to attach TTL to enti
@cassandra.apache.org
Subject: Re: size tiered compaction - improvement
> Any compaction pass over A will first convert the TTL data into tombstones.
>
> Then, any subsequent pass that includes A *and all other sstables
> containing rows with the same key* will drop the tombstones.
thats why i
Any compaction pass over A will first convert the TTL data into tombstones.
Then, any subsequent pass that includes A *and all other sstables
containing rows with the same key* will drop the tombstones.
thats why i proposed to attach TTL to entire CF. Tombstones would not be
needed
On Tue, Apr 17, 2012 at 11:26 PM, Igor wrote:
> You absolutely can. That's what the "user defined" part is: you give
> it the exact list of sstables you want compacted.
>
> does it mean that I can use list (not just one) of sstables as second
> parameter for userDefinedCompaction?
If you want th
Thank you Jonatathan, I missed this point about converting TTL data to
tombstones first.
When you say:
You absolutely can. That's what the "user defined" part is: you give
it the exact list of sstables you want compacted.
does it mean that I can use list (not just one) of sstables as se
On Sat, Apr 14, 2012 at 4:08 AM, Igor wrote:
> Assume I insert all my data with TTL=2weeks and let we have sstable A which
> was created week ago at the time T, so I know that right now it contain:
>
> 1) some data that were inserted not later than T and may-be not expired yet
> 2) some amount of
On Sat, Apr 14, 2012 at 3:27 AM, Radim Kolar wrote:
> forceUserDefinedCompaction would be more usefull if you could do compaction
> on 2 tables.
You absolutely can. That's what the "user defined" part is: you give
it the exact list of sstables you want compacted.
--
Jonathan Ellis
Project Chai
I'll try to explain in more details:
Assume I insert all my data with TTL=2weeks and let we have sstable A
which was created week ago at the time T, so I know that right now it
contain:
1) some data that were inserted not later than T and may-be not expired yet
2) some amount of data that wer
Dne 4.4.2012 6:52, Igor napsal(a):
Here is small python script I run once per day. You have to adjust
size and/or age limits in the 'if' operator. Also I use mx4j interface
for jmx calls.
forceUserDefinedCompaction would be more usefull if you could do
compaction on 2 tables. If i run it on sin
b2.urlopen(url)
time.sleep(1)
if __name__=='__main__':
main()
On 04/04/2012 07:47 AM, i...@4friends.od.ua wrote:
The first is keyspace name, second is sstable name (like
transaction-hc-1024-Data.db
-----Original Message-
From: Radim Kolar
To: user@c
The first is keyspace name, second is sstable name (like
transaction-hc-1024-Data.db
-Original Message-
From: Radim Kolar
To: user@cassandra.apache.org
Sent: Wed, 04 Apr 2012 3:14
Subject: Re: size tiered compaction - improvement
Dne 3.4.2012 23:04, i...@4friends.od.ua napsal(a
Dne 3.4.2012 23:04, i...@4friends.od.ua napsal(a):
if you know for sure that you will free lot of space compacting some
old table, then you can call UserdefinedCompaction for this table(you
can do this from cron). There is also a ticket in jira with discussion
on per-sstable expierd column an
Twitter tried a timestamp-based compaction strategy in
https://issues.apache.org/jira/browse/CASSANDRA-2735. The conclusion
was, "this actually resulted in a lot more compactions than the
SizeTieredCompactionStrategy. The increase in IO was not acceptable
for our use and therefore stopped working
-
From: Radim Kolar
To: user@cassandra.apache.org
Sent: Tue, 03 Apr 2012 22:53
Subject: size tiered compaction - improvement
there is problem with size tiered compaction design. It compacts
together tables of similar size.
sometimes it might happen that you will have some sstables sitting on
there is problem with size tiered compaction design. It compacts
together tables of similar size.
sometimes it might happen that you will have some sstables sitting on
disk forever (Feb 23) because no other similar sized tables were created
and probably never be. because flushed sstable is abo
18 matches
Mail list logo
