cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-6905) commitlog archive replay should attempt to replay all mutations
Date Fri, 25 Jul 2014 15:48:39 GMT

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

Brandon Williams resolved CASSANDRA-6905.
-----------------------------------------

    Resolution: Fixed
      Reviewer: Brandon Williams

LGTM, I committed your test.  Not sure when since March this changed, but good enough for
me.

> commitlog archive replay should attempt to replay all mutations
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-6905
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6905
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Ala' Alkhaldi
>            Priority: Minor
>             Fix For: 2.0.10
>
>         Attachments: CASSANDRA-6905-test.txt
>
>
> Currently when you do a point-in-time recovery using archived commitlogs, the replay
stops when the time is encountered, but since timestamps are supplied by the client we can't
guarantee the segment is ordered by timestamp, so some mutations can be lost.  Instead we
could continue past the given timestamp, and just filter out any mutations greater than it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message