You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/02/14 19:23:12 UTC

[jira] [Updated] (CASSANDRA-6455) Improve concurrency of repair process

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

Aleksey Yeschenko updated CASSANDRA-6455:
-----------------------------------------
    Labels: docs  (was: )

> Improve concurrency of repair process
> -------------------------------------
>
>                 Key: CASSANDRA-6455
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6455
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 3.0
>
>         Attachments: 6455-3.0-v2.txt, 6455-3.0.txt, 6455-tinyfix.patch, 6455.txt
>
>
> Currently, most of the repair tasks (taking snapshots, send/receiving merkle tree, compute MT difference, etc) are done on single threaded AntiEntropyStage.
> This causes a problem like CASSANDRA-6415 and likely to cause unnecessary wait.
> Also, repair is done one CF at the time. I think we can parallelize this(concurrency is configurable by a user based on # of CF and load of the nodes) for faster processing.



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