[
https://issues.apache.org/jira/browse/CASSANDRA-11491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-11491:
------------------------------------
Assignee: Paulo Motta
Priority: Major (was: Minor)
> 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
> Assignee: Paulo Motta
>
> 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)
