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

Timothee Maret updated SLING-9482:
----------------------------------
    Fix Version/s:     (was: Content Distribution Journal Core 0.1.20)
                   Content Distribution Journal Core 0.1.16

> Seed the cache from offset persisted in the source repository
> -------------------------------------------------------------
>
>                 Key: SLING-9482
>                 URL: https://issues.apache.org/jira/browse/SLING-9482
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.16
>
>
> The approach taken in SLING-9460 to avoid sending seeding messages does not 
> address some scenarios like publishing content without subscriber agents. 
> Without subscriber agents.
> To be sure we always have a recent seed available, we should persist seed 
> offsets in the source repository (typ. author) and seed caches from it. We do 
> have the local store class that allows to easily write the offsets in the 
> repository. To not stress the repository too much, we should batch those 
> writes (e.g. 1 offset update every 10 package processed). To support a 
> cluster, the writes must be initiated only from the cluster leader instance.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to