[jira] [Commented] (CASSANDRA-9621) Repair of the SystemDistributed keyspace creates a non-trivial amount of memory pressure

["Tyler Hobbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593594#comment-14593594 ] 

Tyler Hobbs commented on CASSANDRA-9621:
----------------------------------------

Maybe we should skip that keyspace, but CASSANDRA-9491 is really the root cause that needs to be fixed, I think.  With that fixed, there is less reason to do this.

> Repair of the SystemDistributed keyspace creates a non-trivial amount of memory pressure
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9621
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9621
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.2.0 rc2
>
>
> When a repair without any particular option is triggered, the {{SystemDistributed}} keyspace is repaired for all range, and in particular the {{repair_history}} table. For every range, that table is written and flushed (as part of normal repair), meaning that every range triggers the creation of a new 1MB slab region (this also triggers quite a few compactions that also write and flush {{compaction_progress}} at every start and end).
> I don't know how much of a big deal this will be in practice, but I wonder if it's really useful to repair the {{repair_*}} tables by default so maybe we could exclude the SystemDistributed keyspace from default repairs and only repair it if asked explicitly?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)