You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/06/05 08:17:04 UTC
[jira] [Resolved] (IGNITE-5322) Improve WAL record/iterator
structure
[ https://issues.apache.org/jira/browse/IGNITE-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk resolved IGNITE-5322.
--------------------------------------
Resolution: Fixed
> Improve WAL record/iterator structure
> -------------------------------------
>
> Key: IGNITE-5322
> URL: https://issues.apache.org/jira/browse/IGNITE-5322
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.1
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Labels: important
> Fix For: 2.1
>
>
> Currently, we rely on the WAL files layout and zero-ing to make a decision when to stop the iteration.
> Instead, we should write a WAL Pointer to each record with it's position in the file. This will allow us to verify that we are reading a consistent records sequence and should also remove a requirement for zero-clean WAL segment.
> When iterating over the WAL, we should calculate expected next WAL pointer and check that read pointer is equal to the read. If we found a difference, this means that we encountered a stale segment and can stop the iteration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)