You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Roxana-Elena Balasoiu (Jira)" <ji...@apache.org> on 2022/02/08 13:16:00 UTC

[jira] [Commented] (SLING-10583) Ensure o/a/s/d/a/p/distributed events are raised at least once

    [ https://issues.apache.org/jira/browse/SLING-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488833#comment-17488833 ] 

Roxana-Elena Balasoiu commented on SLING-10583:
-----------------------------------------------

This is the PR [https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/97] that I opened for this issue.

> Ensure o/a/s/d/a/p/distributed events are raised at least once
> --------------------------------------------------------------
>
>                 Key: SLING-10583
>                 URL: https://issues.apache.org/jira/browse/SLING-10583
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.24
>
>
> The org/apache/sling/distribution/agent/package/distributed events are raised by computing offset ranges from the discovery topic. Events can be lost in the edge case where no author service is available to compute offset ranges. Ensuring event delivery in that case could be done by persisting the offset of the last event raised and include that information when computing the events to be raised.



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