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/12/31 08:22:00 UTC

[jira] [Commented] (IGNITE-12514) WAL don't flush several last records in LOG-ONLY/FSYNC mode if flush ptr=null

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

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

{panel:title=Branch: [pull/7219/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=4893135&amp;buildTypeId=IgniteTests24Java8_RunAll]

> WAL don't flush several last records in LOG-ONLY/FSYNC mode if flush ptr=null
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-12514
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12514
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>             Fix For: 2.9
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the current implementation, last flush pointer dependent to thread-local. If some thread adds new records and another thread calls wal.flush(null), this flush may not be flushed records witch was added in thread one, because in case null flush pointer, thread flushed until the last record which was added in current thread.



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