Re: repair_history maintenance
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 Lohfinkwrote: > 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, sfesc...@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
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, sfesc...@gmail.comwrote: > 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? >
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?