[
https://issues.apache.org/jira/browse/SLING-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379756#comment-14379756
]
Bertrand Delacretaz commented on SLING-4533:
--------------------------------------------
Ok thanks for the info - having a reliable warning if events might be lost is
essential IMO as those are very tricky things to troubleshoot. If you have
ideas about how that can be implemented it would be good to create an Oak
ticket.
> OakResourceListener does not allow to configure the OAK observation queue
> length
> --------------------------------------------------------------------------------
>
> Key: SLING-4533
> URL: https://issues.apache.org/jira/browse/SLING-4533
> Project: Sling
> Issue Type: Bug
> Components: JCR, Oak
> Affects Versions: JCR Resource 2.5.0
> Reporter: Marc Pfaff
>
> Currently the OakResourceListener does not allow to configure the OAK
> observation queue length when instantiating the OAK BackgroundObserver. Thus
> the default queue size of 1000 is used.
> If the max queue size is reached, OAK seem's to turn the observation in a
> 'graceful degratation' mode, which leads to a compacted view of observations.
> Means, not every single observation makes it to the observer no more. From
> the point of view of the Sling resource changed events, this looks like some
> events are missing.
> I would propose to make the OAK observation queue size configurable in order
> to have the possibility to avoid 'graceful degratation'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
