Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 20 Oct 2014 11:07:34 +0000 (UTC)
From: "Branimir Lambov (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12714328.1400106269000.295624.1413803254015@Atlassian.JIRA>
In-Reply-To: <JIRA.12714328.1400106269000@Atlassian.JIRA>
References: <JIRA.12714328.1400106269000@Atlassian.JIRA>
 <JIRA.12714328.1400106269637@arcas>
Subject: [jira] [Updated] (CASSANDRA-7237) Optimize batchlog manager to
 avoid full scans
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Branimir Lambov updated CASSANDRA-7237:
---------------------------------------
    Fix Version/s:     (was: 2.1.2)
                   3.0

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