You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/19 12:14:00 UTC
[jira] [Commented] (IGNITE-7754) WAL in LOG_ONLY mode doesn't
execute fsync on checkpoint begin
[ https://issues.apache.org/jira/browse/IGNITE-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404697#comment-16404697 ]
ASF GitHub Bot commented on IGNITE-7754:
----------------------------------------
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/3656
IGNITE-7754 dirty fix for FSYNC on archivation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7754
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3656.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 #3656
----
commit 8d7b64da584e95d951d89c357b8d96f41c173a0d
Author: Ivan Rakov <iv...@...>
Date: 2018-03-19T12:11:21Z
IGNITE-7754 dirty fix for FSYNC on archivation
----
> WAL in LOG_ONLY mode doesn't execute fsync on checkpoint begin
> --------------------------------------------------------------
>
> Key: IGNITE-7754
> URL: https://issues.apache.org/jira/browse/IGNITE-7754
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Ilya Lantukh
> Assignee: Ivan Rakov
> Priority: Critical
> Fix For: 2.5
>
>
> On checkpoint begin method IgniteWriteAheadLogManager.fsync(WALPointer ptr) will be called, but it won't actually perform fsync because mode isn't FSYNC. It might lead to LFS corruption if OS or hardware failed until checkpoint had been finished.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)