[jira] [Commented] (GEODE-2679) Lucene asynchronous disk writes for aeq can lead to data mismatch after compacting

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on GEODE-2679:
--------------------------------------------------------

Commit 17877689beee29671c143baba7c3d65e917205fe in geode's branch refs/heads/develop from [~huynhja]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=1787768 ]

GEODE-2679: Lucene asynchronous disk writes for aeq can lead to data mismatch after compacting

* forcing disk sync = true for Lucene AEQ


> Lucene asynchronous disk writes for aeq can lead to data mismatch after compacting
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-2679
>                 URL: https://issues.apache.org/jira/browse/GEODE-2679
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>
> Due to the way krf and drf oplogs are created/updated, if the aeq has disk synchronous as false, there is a window of time where a krf is rolled/created with the current region entries, but events that had been removed have not yet been written to the drf.
> We should probably change the aeq to be disk sync = true.  This will alleviate some of the data mismatch where we have potential extra keys after compacting the oplogs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)