[jira] [Updated] (CASSANDRA-13290) Optimizing very small repair streams

["C. Scott Andreas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

C. Scott Andreas updated CASSANDRA-13290:
-----------------------------------------
    Component/s: Repair

> Optimizing very small repair streams
> ------------------------------------
>
>                 Key: CASSANDRA-13290
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13290
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Repair
>            Reporter: Benjamin Roth
>            Priority: Major
>
> I often encountered repair scenarios, where a lot of tiny repair streams were created. This results in hundrets, thousands or even ten-thousands super small SSTables (some bytes to some kbytes).
> This puts a lot of pressure on compaction and may even lead to a crash due to too many open files - I also encountered this.
> What could help to avoid this:
> After CASSANDRA-12888 is resolved, a tiny stream (e.g. < 100kb) could be sent through the write path to be buffered by memtables instead of creating an SSTable each.
> Without CASSANDRA-12888 this would break incremental repairs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org