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 were already close to expiration due TTL at
the time T, but still had no chances to be wiped out because up to the
current moment size-tiered compaction did not involve A into compactions.
Large amount of data from 2) became expired in a week after time T and
probably passed gc_grace period, so it shoould be wiped at any
compaction on table A.
Or I missed something?
On 04/14/2012 11:27 AM, Radim Kolar wrote:
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 single table, it dont shrinks
and it does not solve my problem - having sstables at size which will
be never compacted because no other sstable of similar size will be
created.
