You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/03/30 16:37:53 UTC

[jira] [Resolved] (SLING-4533) OakResourceListener does not allow to configure the OAK observation queue length

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

Carsten Ziegeler resolved SLING-4533.
-------------------------------------
    Resolution: Fixed

Thanks for your patch, Marc - it's applied

> 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
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.5.2
>
>         Attachments: SLING-4533-improved.patch, SLING-4533.patch
>
>
> 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)