[jira] [Updated] (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:all-tabpanel ] Ivan Rakov updated IGNITE-7754: --- Attachment: screenshot-2.png > 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 > > Attachments: image-2018-03-20-19-08-42-234.png, screenshot-1.png, > screenshot-2.png > > > 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)
[jira] [Updated] (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:all-tabpanel ] Ivan Rakov updated IGNITE-7754: --- Attachment: screenshot-1.png > 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 > > Attachments: image-2018-03-20-19-08-42-234.png, screenshot-1.png > > > 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)
[jira] [Updated] (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:all-tabpanel ] Ivan Rakov updated IGNITE-7754: --- Attachment: image-2018-03-20-19-08-42-234.png > 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 > > Attachments: image-2018-03-20-19-08-42-234.png > > > 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)
[jira] [Updated] (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:all-tabpanel ] Dmitriy Setrakyan updated IGNITE-7754: -- Fix Version/s: 2.5 > 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)
[jira] [Updated] (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:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7754: --- Component/s: persistence > 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: Ilya Lantukh >Priority: Critical > > 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)
