You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by "sfescape@gmail.com" <sf...@gmail.com> on 2016/09/22 18:28:07 UTC

repair_history maintenance

Should there be a maintenance schedule for repair_history? Meaning, a
scheduled nodetool repair and/or deletion schedule? Or is it the intention
that this table just grow for the life of the cluster?

Re: repair_history maintenance

Posted by "sfescape@gmail.com" <sf...@gmail.com>.

That sounds good to me. Unless there are objections I'll start doing that
on a scheduled bases.

Cheers

On Fri, Sep 23, 2016 at 11:55 AM Chris Lohfink <cl...@gmail.com> wrote:

> Probably should just periodically truncate/clear snapshots when gets too
> big (will probably take months before noticeable). I opened
> https://issues.apache.org/jira/browse/CASSANDRA-12701 for discussion on
> if it should use TTLs
>
> Chris
>
> On Thu, Sep 22, 2016 at 1:28 PM, sfescape@gmail.com <sf...@gmail.com>
> wrote:
>
>> Should there be a maintenance schedule for repair_history? Meaning, a
>> scheduled nodetool repair and/or deletion schedule? Or is it the intention
>> that this table just grow for the life of the cluster?
>>
>
>

Re: repair_history maintenance

Posted by Chris Lohfink <cl...@gmail.com>.

Probably should just periodically truncate/clear snapshots when gets too
big (will probably take months before noticeable). I opened
https://issues.apache.org/jira/browse/CASSANDRA-12701 for discussion on if
it should use TTLs

Chris

On Thu, Sep 22, 2016 at 1:28 PM, sfescape@gmail.com <sf...@gmail.com>
wrote:

> Should there be a maintenance schedule for repair_history? Meaning, a
> scheduled nodetool repair and/or deletion schedule? Or is it the intention
> that this table just grow for the life of the cluster?
>