gt; My experience with TTL columns so far has been pretty similar to
>>>>> Viktor's in that the only way to keep them row count under control is to
>>>>> force major compactions. In real world use, STCS and LCS both leave TTL
>>>>> expired rows around
t; -Bryan
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jan 17, 2013 at 1:47 AM, Viktor Jevdokimov <
>>>> viktor.jevdoki...@adform.com> wrote:
>>>>
>>>>> @Bryan,
>>>>>
>>>>> *
>>
>>>> ** **
>>>>
>>>> Experience with LCS was not successful in our case, data size keeps too
>>>> high along with amount of compactions.
>>>>
>>>> ** **
>>>>
>>>> IMO, before 1.2, LCS was goo
t;
>>> ** **
>>>
>>> IMO, before 1.2, LCS was good for CFs without TTL or high delete rate. I
>>> have not tested 1.2 LCS behavior, we’re still on 1.0.x****
>>>
>>> ** **
>>>
>>> ** **
>>>Best regards / Pagarbiai
&g
;> J. Jasinskio 16C, LT-01112 Vilnius, Lithuania
>> Follow us on Twitter: @adforminsider<http://twitter.com/#!/adforminsider>
>> Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>
>> [image: Adform News] <http://www.adform.com>
>
y for the attention and use of the named addressee and may be
> confidential. If you are not the intended recipient, you are reminded that
> the information remains the property of the sender. You must not use,
> disclose, distribute, copy, print or rely on this e-mail. If you have
&g
hursday, January 17, 2013 06:24
To: user@cassandra.apache.org
Subject: Re: LCS not removing rows with all TTL expired columns
Minor compaction (with Size Tiered) will only purge tombstones if all fragments
of a row are contained in the SSTables being compacted. So if you have a long
lived row,
Minor compaction (with Size Tiered) will only purge tombstones if all fragments
of a row are contained in the SSTables being compacted. So if you have a long
lived row, that is present in many size tiers, the columns will not be purged.
> (thus compacted compacted) 3 days after all columns for
According to the timestamps (see original post) the SSTable was written
(thus compacted compacted) 3 days after all columns for that row had
expired and 6 days after the row was created; yet all columns are still
showing up in the SSTable. Note that the column shows now rows when a
"get" for that
To get column removed you have to meet two requirements
1. column should be expired
2. after that CF gets compacted
I guess your expired columns are propagated to high tier CF, which gets
compacted rarely.
So, you have to wait when high tier CF gets compacted.
Andrey
On Wed, Jan 16, 2013 at 11
On cassandra 1.1.5 with a write heavy workload, we're having problems
getting rows to be compacted away (removed) even though all columns have
expired TTL. We've tried size tiered and now leveled and are seeing the
same symptom: the data stays around essentially forever.
Currently we write all co
11 matches
Mail list logo
