cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-540) Commit log replays should be multithreaded
Date Sat, 14 Nov 2009 02:21:39 GMT

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

Jonathan Ellis updated CASSANDRA-540:
-------------------------------------

    Attachment: 540.patch

fixed NPE (StageManager wasn't initialized in the test because that was being done by StorageService.
 Moved it into SM.)

CDLatch isn't going to work here since we don't know the row count until we're done, and the
first rows are already going to be finished by then.  CompletedTasks will be fine.

> 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, 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