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

Christian Schneider updated SLING-13151:
----------------------------------------
    Description: 
How to reproduce:
 - create content distribution of type delete on path /libs . This will block 
the queue
 - wait two days until the message has been evicted from kafka and content 
distribution service
 - distribution will show on author in queue with 0 retries and no error
 - clearing the queue has no effect

The reason for this is that author queues are not guaranteed to be cleared 
after a certain time. We got a clear timer after 12h but this only triggers 
when the queue is also big.
So for small queues we run into this error.

We should guarantee to clear the author queue cache after 12h irrespective of 
queue size.
h3.

> Always clear queue cache after 12h
> ----------------------------------
>
>                 Key: SLING-13151
>                 URL: https://issues.apache.org/jira/browse/SLING-13151
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.6.0
>
>
> How to reproduce:
>  - create content distribution of type delete on path /libs . This will block 
> the queue
>  - wait two days until the message has been evicted from kafka and content 
> distribution service
>  - distribution will show on author in queue with 0 retries and no error
>  - clearing the queue has no effect
> The reason for this is that author queues are not guaranteed to be cleared 
> after a certain time. We got a clear timer after 12h but this only triggers 
> when the queue is also big.
> So for small queues we run into this error.
> We should guarantee to clear the author queue cache after 12h irrespective of 
> queue size.
> h3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to