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/07/31 14:14:04 UTC

[jira] [Commented] (CASSANDRA-7237) Optimize batchlog manager to avoid full scans

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

Aleksey Yeschenko commented on CASSANDRA-7237:
----------------------------------------------

Could you please rebase - or, rather, reapply - on top of latest trukn, with CASSANDRA-8143 applied?

Thanks.

> Optimize batchlog manager to avoid full scans
> ---------------------------------------------
>
>                 Key: CASSANDRA-7237
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7237
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>            Assignee: Branimir Lambov
>            Priority: Minor
>             Fix For: 3.0.0 rc1
>
>
> Now that we use time-UUIDs for batchlog ids, and given that w/ local strategy the partitions are ordered in time-order here, we can optimize the scanning by limiting the range to replay taking the last replayed batch's id as the beginning of the range, and uuid(now+timeout) as its end.



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