cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11491) Split repair job into tasks per table
Date Mon, 09 May 2016 15:53:13 GMT

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

Paulo Motta commented on CASSANDRA-11491:
-----------------------------------------

Increasing priority of this since this will allow running anti-compactions after each table
is finished, and release sstable references earlier to avoid OOMing when running incremental
repair in multiple tables (or keyspace-level).

> Split repair job into tasks per table
> -------------------------------------
>
>                 Key: CASSANDRA-11491
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11491
>             Project: Cassandra
>          Issue Type: Task
>          Components: Streaming and Messaging
>            Reporter: Paulo Motta
>            Priority: Minor
>
> We currently split a parent repair session into multiple repair sessions, one per range.
Each repair session is further split into multiple repair jobs, one per table.
> As we move into an auto-repair world with CASSANDRA-11190, with repair settings per table,
it will probably simplify things if we reason about repair sessions on a per-table basis.
> Besides simplifying current code, this will simplify adding more advanced scheduling
of repair tasks per table and other optimizations.



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

Mime
View raw message