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

Posted to dev@geode.apache.org by "Jason Huynh (JIRA)" <ji...@apache.org> on 2017/03/16 23:13:41 UTC

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

     [ https://issues.apache.org/jira/browse/GEODE-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Huynh reassigned GEODE-2679:
----------------------------------

    Assignee: Jason Huynh

> 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)