[jira] [Resolved] (SLING-10077) Mode to raise events only locally

["Timothee Maret (Jira)" <ji...@apache.org>]

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

Timothee Maret resolved SLING-10077.
------------------------------------
    Resolution: Fixed

> Mode to raise events only locally
> ---------------------------------
>
>                 Key: SLING-10077
>                 URL: https://issues.apache.org/jira/browse/SLING-10077
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Content Distribution Journal Core 0.1.18
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.24
>
>
> Currently the {{o/a/s/d/a/p/queued}} and {{o/a/s/d/a/p/distributed}} events are raised as local events in each author instance of a cluster. Handling those events in each author instance makes sense for use cases that require maintaining a distributed data structure like a cache. However, some use cases like content invalidation, would need to handle the events only once (deduplicate events).
> Deduplicating events will be done by leveraging the Sling Discovery API. When deduplicating is set, only the leader instance will sent distributed events.
> Prior suggested approach of distributing events through the cluster is not a good option because it could overload the repository due to steady and frequent commits required to support the distribution of events through the cluster.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)