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

Marcus Eriksson commented on CASSANDRA-6455:
--------------------------------------------

Ok, looks good to me

I got the exception below once during testing, but couldn't reproduce it, so I 
don't know if I messed up my testing or if there is a race somewhere

{code}
ERROR [AntiEntropyStage:1] 2014-07-02 11:25:44,745 CassandraDaemon.java:166 - 
Exception in thread Thread[AntiEntropyStage:1,5,main]
java.lang.AssertionError: null
        at 
org.apache.cassandra.repair.RepairSession.validationComplete(RepairSession.java:168)
 ~[main/:na]
        at 
org.apache.cassandra.service.ActiveRepairService.handleMessage(ActiveRepairService.java:369)
 ~[main/:na]
        at 
org.apache.cassandra.repair.RepairMessageVerbHandler.doVerb(RepairMessageVerbHandler.java:128)
 ~[main/:na]
        at 
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:62) 
~[main/:na]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
~[na:1.7.0_55]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
~[na:1.7.0_55]
        at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_55]
{code}

> 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.txt, 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.2#6252)

Reply via email to