Does this disk-sync=true really change anything? My understanding is all that does is cause us to flush the linux disk buffers after every write. I'm not aware of it changing behavior in terms of buffering inside Geode.
-- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Mon, Mar 20, 2017 at 4:13 PM, Jason Huynh (JIRA) <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/GEODE-2679?page= > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Jason Huynh resolved GEODE-2679. > -------------------------------- > Resolution: Fixed > Fix Version/s: 1.1.0 > > > 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 > > Fix For: 1.1.0 > > > > > > 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) >
