i see leveled compaction used, if it's last, it will have to stay until
next level compaction happens, then will be gone, right ?
On Thu, Feb 1, 2018 at 2:33 AM, Bo Finnerup Madsen
wrote:
> Hi,
>
> We are running a small 9 node Cassandra v2.1.17 cluster. The cluster
> generally runs fine, but we
Changing the defaul TTL doesn’t change the TTL on the existing data, only
new data. It’s only set if you don’t supply one yourself.
On Wed, Jan 31, 2018 at 11:35 PM Bo Finnerup Madsen
wrote:
> Hi,
>
> We are running a small 9 node Cassandra v2.1.17 cluster. The cluster
> generally runs fine, but
[mailto:j...@jonhaddad.com]
Sent: Thursday, February 01, 2018 11:29 AM
To: user@cassandra.apache.org
Subject: Re: Old tombstones not being cleaned up
Changing the defaul TTL doesn’t change the TTL on the existing data, only new
data. It’s only set if you don’t supply one yourself.
On Wed, Jan 31
I have forced several compactions without the tombstones being cleaned.
Compactions was forced both using "nodetool compact" and by changeing
compaction algorithem from leved to sizedtiered and back...
tor. 1. feb. 2018 kl. 15.54 skrev James Shaw :
> i see leveled compaction used, if it's last, i
We do not use TTL anywhere...records are inserted and deleted "manually" by
our software.
tor. 1. feb. 2018 kl. 18.29 skrev Jonathan Haddad :
> Changing the defaul TTL doesn’t change the TTL on the existing data, only
> new data. It’s only set if you don’t supply one yourself.
>
> On Wed, Jan 31,
f tombstones!
>
>
>
>
>
> *From:* Jonathan Haddad [mailto:j...@jonhaddad.com]
> *Sent:* Thursday, February 01, 2018 11:29 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Old tombstones not being cleaned up
>
>
>
> Changing the defaul TTL doesn’t change
the
partition anymore after a topology change (e.g. scale out beyond the keyspace
RF).
Just a very wild guess.
Thomas
From: Bo Finnerup Madsen [mailto:bo.gunder...@gmail.com]
Sent: Donnerstag, 01. Februar 2018 22:14
To: user@cassandra.apache.org
Subject: Re: Old tombstones not being cleaned up
M
To: user@cassandra.apache.org
Subject: Re: Old tombstones not being cleaned up
I, almost, tried that today :) I ran a repair, changed the compaction algorithm
from leveled to sizetierd and back. This definitely forced a compaction, but
the tombstones are still there.
Will setting
lto:bo.gunder...@gmail.com]
> *Sent:* Donnerstag, 01. Februar 2018 22:14
>
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Old tombstones not being cleaned up
>
>
>
> We do not use TTL anywhere...records are inserted and deleted "manually"
> by our softwar
Right. In this case, cleanup should have done the necessary work here.
Thomas
From: Bo Finnerup Madsen [mailto:bo.gunder...@gmail.com]
Sent: Freitag, 02. Februar 2018 06:59
To: user@cassandra.apache.org
Subject: Re: Old tombstones not being cleaned up
We did start with a 3 node cluster and a RF
e, cleanup should have done the necessary work here.
>>
>>
>>
>> Thomas
>>
>>
>>
>> From: Bo Finnerup Madsen [mailto:bo.gunder...@gmail.com]
>> Sent: Freitag, 02. Februar 2018 06:59
>>
>>
>> To: user@cassandra.apache.
.steinmau...@dynatrace.com>:
>
>> Right. In this case, cleanup should have done the necessary work here.
>>
>>
>>
>> Thomas
>>
>>
>>
>> *From:* Bo Finnerup Madsen [mailto:bo.gunder...@gmail.com]
>> *Sent:* Freitag, 02. Februar 2018 06:
..@dynatrace.com>:
>
>> Right. In this case, cleanup should have done the necessary work here.
>>
>>
>>
>> Thomas
>>
>>
>>
>> *From:* Bo Finnerup Madsen [mailto:bo.gunder...@gmail.com]
>> *Sent:* Freitag, 02. Februar 2018 06:59
>>
>>
I "fixed" it by dropping and
>> re-creating the table.
>>
>> fre. 2. feb. 2018 kl. 07.29 skrev Steinmaurer, Thomas <
>> thomas.steinmau...@dynatrace.com>:
>>
>>> Right. In this case, cleanup should have done the necessary work here.
>>&
l nodes,
>>>> would that not have removed any stray partitions?
>>>>
>>>> tor. 1. feb. 2018 kl. 22.31 skrev Steinmaurer, Thomas <
>>>> thomas.steinmau...@dynatrace.com>:
>>>>
>>>> Did you started with a 9 node cluster from the beginning or d
15 matches
Mail list logo
