You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/06/19 12:18:00 UTC
[jira] [Created] (CASSANDRA-9621) Repair of the SystemDistributed
keyspace creates a non-trivial amount of memory pressure
Sylvain Lebresne created CASSANDRA-9621:
-------------------------------------------
Summary: 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
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)