[
https://issues.apache.org/jira/browse/GEODE-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239869#comment-15239869
]
Robert Geiger commented on GEODE-1209:
--------------------------------------
In the case of an eviction or expiration that is intended only to conserve
memory space by removing least used keys it does not seem to be required to
support propagation of these events to the underlying cache store. In the case
where data has a time to live that applies globally (both in memory and in
persistent storage), and that TTL expires, it would seem it is desirable to
support such a method for the expiration event to be propagated so that the
item can be removed from the cache stores.
> Support/Propagating eviction and expiration operation with AsycEventQueue.
> --------------------------------------------------------------------------
>
> Key: GEODE-1209
> URL: https://issues.apache.org/jira/browse/GEODE-1209
> Project: Geode
> Issue Type: Bug
> Components: wan
> Reporter: Anilkumar Gingade
>
> The AsyncEventQueue works as a write-behind cache event handler to
> synchronize region updates with other source...Currently it does not support
> distribution of eviction or expiration operation....This makes the external
> source to be out of sync with data that has been removed/invalidated through
> eviction and expiration.
> This ticket is to add/support eviction and expiration operation with
> AsyncEventQueue, so that all the operations are propagated to
> AsyncEventQueueListener and the usage of those events are left to underlying
> implementation/applications(like WAN, Lucene, plug-able storage, etc).
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/events/implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
