ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Muzafarov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-11074) Implement catch-up temporary WAL
Date Sun, 24 Feb 2019 11:08:00 GMT

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

Maxim Muzafarov updated IGNITE-11074:
    Ignite Flags:   (was: Docs Required)

> Implement catch-up temporary WAL
> --------------------------------
>                 Key: IGNITE-11074
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11074
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Major
>              Labels: iep-28
> While the demander node is in the partition file transmission state it must save all
cache entries corresponding to the moving partition into a new temporary WAL storage. These
entries will be applied later one by one on the received cache partition file. All asynchronous
operations will be enrolled to the end of temporary WAL storage during storage reads until
it becomes fully read. The file-based FIFO approach assumes to be used by this process.
> The new write-ahead-log manager for writing temporary records must support to:
> Unlimited number of wal-files to store temporary data records;
> Iterating over stored data records during an asynchronous writer thread inserts new records;
> WAL-per-partiton approach needs to be used;
> Write operations to temporary WAL storage must have higher priority over reading operations;

This message was sent by Atlassian JIRA

View raw message