jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-4522) Improve CommitRateLimiter to optionally block some commits
Date Mon, 18 Jul 2016 14:15:20 GMT

    [ https://issues.apache.org/jira/browse/OAK-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382335#comment-15382335
] 

Michael Dürig commented on OAK-4522:
------------------------------------

I think to come up with a proper "commit rate limiter" we need to be able to control commits
in a more sophisticated way than we are doing it in the current implementation. See OAK-4122
for initial ideas. 

> 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)

Mime
View raw message