[GEODE-7121] Controlling event dispatch to AsyncEventListener

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.11.0
• Fix Version/s: 1.10.0, 1.11.0
• Labels: AsyncEventQueues GeodeCommons
• Assignee: Unassigned
• Reporter: Anilkumar Gingade
• Created: 23/Aug/19 18:57
• Updated: 18/Sep/19 22:22
• Resolved: 18/Sep/19 22:22

Description

The Geode system requires AEQs to be configured before regions are created. If an AEQ listener is operating on a secondary region, this could cause listener to operate on a region which is not yet created or fully initialized (for region with co-located regions) which could result in missing events or dead-lock scenario between region creation threads (creating regions and its co-located regions in the listener). This scenario is likely to happen during persistence recovery; when AEQs are created in the start, the recovered AEQ events are dispatched immediately, thus invoking the AEQ listeners.

Issue Links

• mentioned in: Page Loading...

Sub-Tasks

• Ability to create AEQ in a paused state: Closed
• Ability to resume/unpause an AEQ if it has been paused: Closed
• XML and cluster config changes for creating AEQ in a paused state: Closed
• Add GFSH arguments for starting AEQ in a paused state: Closed
• AsyncEventQueueMXBean to provide AsyncEventQueue's dispatcher status: Closed
• Add GFSH command for resuming an AEQ from a paused state: Closed
• Alter command to change the state of event processing during AEQ creation: Closed
• Add documentation for Asynchronous Event Queue pause-event-processing configuration: Closed