You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2017/06/17 18:04:20 UTC

[jira] [Closed] (GEODE-2745) The AsyncEventQueueImpl waitUntilFlushed method waits longer than it should for events to be flushed

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

Anthony Baker closed GEODE-2745.
--------------------------------

> The AsyncEventQueueImpl waitUntilFlushed method waits longer than it should for events to be flushed
> ----------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2745
>                 URL: https://issues.apache.org/jira/browse/GEODE-2745
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Barry Oglesby
>            Assignee: Shelley Lynn Hughes-Godfrey
>             Fix For: 1.2.0
>
>
> With the changes to waitUntilFlushed to process 10 buckets at a time, if events are happening while waitUntilFlushed is in progress, then all the buckets after the first 10 will have processed more than it should before returning.
> If the update rate is causing the queue to always contain 113000 events, and the events are spread evenly across the buckets, each bucket will have 1000 events to wait for. The first 10 buckets will wait for their 1000 events. When those have been processed, the next 10 buckets will wait for their 1000 events starting from that point, but they've already processed 1000 events. So, these buckets will actually wait for 2000 events to be processed before returning. This pattern continues until all the buckets are done.
> The WaitUntilBucketRegionQueueFlushedCallable needs to track not only the BucketRegionQueue but also the latestQueuedKey.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)