[
https://issues.apache.org/jira/browse/CASSANDRA-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-6455:
---------------------------------------
Attachment: 6455-tinyfix.patch
+1, attaching tiny fix to the options checking in StorageService
I think we should also move the anticompaction stuff out of StorageService and
into ActiveRepairService (or even RepairSession) and make it run in parallel
(ie obey the -j parameter), but i'm totally fine doing that in another ticket
(will create)
> 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)
