cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7237) Optimize batchlog manager to avoid full scans
Date Sun, 02 Aug 2015 20:26:05 GMT

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

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

This is next in my review queue. For now, only committed the latest commit (the dtest regressions
fix) to trunk as {{6aa7d6ce89f155b72111bffce54e9bee66080b03}}.

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

Mime
View raw message