You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2017/12/05 08:45:00 UTC

[jira] [Assigned] (IGNITE-7017) Reconsider WAL archive strategy

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

Dmitriy Pavlov reassigned IGNITE-7017:
--------------------------------------

    Assignee: Dmitriy Pavlov

> Reconsider WAL archive strategy
> -------------------------------
>
>                 Key: IGNITE-7017
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7017
>             Project: Ignite
>          Issue Type: Task
>    Affects Versions: 2.3
>            Reporter: Alexey Goncharuk
>            Assignee: Dmitriy Pavlov
>             Fix For: 2.4
>
>
> Currently, we write WAL files in work directory and then copy them to the archive after the segment is closed. 
> This was done to overcome XFS bug which leads to a double fsync cost immediately after file creation. This approach leads to excessive disk usage and can be optimized, especially for LOG_ONLY mode.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)