[
https://issues.apache.org/jira/browse/CASSANDRA-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573691#comment-14573691
]
Aleksey Yeschenko commented on CASSANDRA-7237:
----------------------------------------------
The difference is that in CASSANDRA-6230 we can split by hosts, and that
CASSANDRA-6230 requires no removals. Whole files get removed with hints,
individual records for batchlog.
What this issue does is make batchlog replay efficient, and allow us to perform
it much more often - reducing the latency.
So, my question is, is it important for materialized views - as currently
implemented - or not?
If yes, then this should be bumped to 3.0beta1. If not, then CASSANDRA-8143, a
prerequisite for this ticket, can be pushed to 3.X.
> 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)
