cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-540) Commit log replays should be multithreaded
Date Fri, 13 Nov 2009 23:31:39 GMT

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

Stu Hood commented on CASSANDRA-540:
------------------------------------

Rather than sleeping until the number of items completed is larger than rows, you could initialize
a http://java.sun.com/javase/6/docs/api/index.html?java/util/concurrent/CountDownLatch.html,
and then block for completion.

Additionally, this approach will hang forever if one of the entries in the commitlog is corrupt,
won't it?

> Commit log replays should be multithreaded
> ------------------------------------------
>
>                 Key: CASSANDRA-540
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-540
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: any
>            Reporter: Brandon Williams
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 540.patch
>
>
> Commit log replays are currently single threaded.  This makes log replay speed limited
when restarting a cassandra node.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message