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

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2019/09/26 15:43:00 UTC

[jira] [Commented] (IGNITE-12231) RollbackRecord's must be flushed after logging to WAL

    [ https://issues.apache.org/jira/browse/IGNITE-12231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938739#comment-16938739 ] 

Ignite TC Bot commented on IGNITE-12231:
----------------------------------------

{panel:title=Branch: [pull/6908/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4633828&amp;buildTypeId=IgniteTests24Java8_RunAll]

> RollbackRecord's must be flushed after logging to WAL
> -----------------------------------------------------
>
>                 Key: IGNITE-12231
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12231
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey N. Gura
>            Assignee: Andrey N. Gura
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Every record or records batch logged to WAL must call {{wal().flush()}} in order to save data on storage device.
> {{TxPartitionCounterStateOnePrimaryTwoBackupsHistoryRebalanceTest.testPartialPrepare_2TX_1_1}} test fails periodically with disabled MMAP.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)