cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-7237) Optimize batchlog manager to avoid full scans
Date Fri, 05 Jun 2015 15:15:01 GMT

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

Carl Yeksigian edited comment on CASSANDRA-7237 at 6/5/15 3:14 PM:
-------------------------------------------------------------------

I don't think this is going to be necessary for MV to work properly - it's possible we will
still need this to make them work efficiently. I think that leaving this in 3.x is fine at
this point, since it isn't necessary for the first version at least.


was (Author: carlyeks):
I don't think this is going to be necessary for MV to work properly - it's possible we will
still need this to make them work efficiently. I think that leaving this in 3.x is fine at
this point, since it is necessary for the first version at least.

> 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.x
>
>
> 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