[
https://issues.apache.org/jira/browse/SLING-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-11914:
----------------------------------------
Description:
When DistributionSubscriber does not yet have a stored offset it is in a
problematic state.
When a package message is sent and DistributionSubscriber starts late or
restarts it might miss the message.
This issue aim to improve the situation by accepting offsets via OffsetMessage.
The messaging provider can send such a message immediately when the poller is
created to inform subscriber about the current offset on the topic. This offset
is then written to repository.
>From this point in time the timing problem is solved. No message after the
>stored offset can be lost.
was:
When DistributionSubscriber does not yet have a stored offset it is in a
problematic state.
When a package message is sent and DistributionSubscriber starts late or
restarts it might miss the message.
This issue aim to improve the situation by accepting offsets via ping messages.
The messaging provider can send such a message immediately when the poller is
created to inform subscriber about the current offset on the topic. This offset
is then written to repository.
>From this point in time the timing problem is solved. No message after the
>stored offset can be lost.
> Accept initial offset via OffsetMessage
> ---------------------------------------
>
> Key: SLING-11914
> URL: https://issues.apache.org/jira/browse/SLING-11914
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Priority: Major
>
> When DistributionSubscriber does not yet have a stored offset it is in a
> problematic state.
> When a package message is sent and DistributionSubscriber starts late or
> restarts it might miss the message.
> This issue aim to improve the situation by accepting offsets via
> OffsetMessage. The messaging provider can send such a message immediately
> when the poller is created to inform subscriber about the current offset on
> the topic. This offset is then written to repository.
> From this point in time the timing problem is solved. No message after the
> stored offset can be lost.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
