[
https://issues.apache.org/jira/browse/IGNITE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278271#comment-16278271
]
ASF GitHub Bot commented on IGNITE-7017:
----------------------------------------
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/3140
IGNITE-7017: Archiver disabled WAL mode in case folders are equal
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7017
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3140
----
commit 3edcf672d9b15cd46cf195326c4221be64c6374a
Author: dpavlov <[email protected]>
Date: 2017-12-05T09:27:22Z
IGNITE-7017: Archiver disabled WAL mode in case folders are equal
----
> 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)
