You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Yuji Ito <yu...@phact-columba.com> on 2018/08/30 03:14:31 UTC

TTL of paxos table

Hi,

I wonder why records on the system.paxos table aren't removed, though all
records are updated with TTL (at least 3 hours).
That's because gc_grace_seconds of system.paxos table is always 0 and users
can't change that value of System keyspace!

Why is the TTL of paxos record invalidated?
Or, I'm misunderstanding?

Related to:
https://issues.apache.org/jira/browse/CASSANDRA-5451
https://issues.apache.org/jira/browse/CASSANDRA-13548

Thanks,
Yuji

Re: TTL of paxos table

Posted by kurt greaves <ku...@instaclustr.com>.
It's just that compaction hasn't occured. TTL works even though GCGS is 0.
There's been multiple discussions around this in the past, but we haven't
come to a consensus yet though. Some proposals to change compaction
strategy, some want to make it customisable. Treating paxos as sub-tables
has also come up and the improvements listed in CASSANDRA-13548.
TBH we should probably do 13548 and see where that gets us.

On 30 August 2018 at 13:14, Yuji Ito <yu...@phact-columba.com> wrote:

> Hi,
>
> I wonder why records on the system.paxos table aren't removed, though all
> records are updated with TTL (at least 3 hours).
> That's because gc_grace_seconds of system.paxos table is always 0 and users
> can't change that value of System keyspace!
>
> Why is the TTL of paxos record invalidated?
> Or, I'm misunderstanding?
>
> Related to:
> https://issues.apache.org/jira/browse/CASSANDRA-5451
> https://issues.apache.org/jira/browse/CASSANDRA-13548
>
> Thanks,
> Yuji
>