[
https://issues.apache.org/jira/browse/OAK-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355408#comment-15355408
]
Stefan Egli commented on OAK-4522:
----------------------------------
yes, and from this I conclude that you can't have a hard limit on observation
queues - or at least that's making the situation more difficult. As we agree
one shouldn't block the listeners, as they would help reducing the queues. But
then, what if such a listener does a few commits that would result in a queue
overflow? Hence I think having a hard limit is difficult and perhaps should not
be applied for listeners, but only for 'normal' clients.
> Improve CommitRateLimiter to optionally block some commits
> ----------------------------------------------------------
>
> Key: OAK-4522
> URL: https://issues.apache.org/jira/browse/OAK-4522
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
>
> The CommitRateLimiter of OAK-1659 can delay commits, but doesn't currently
> block them, and delays even those commits that are part of handling events.
> Because of that, the queue can still get full, and possibly delaying commits
> while handling events can make the situation even worse.
> In Jackrabbit 2.x, we had a similar feature: JCR-2402. Also related is
> JCR-2746.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
