You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/01/16 16:46:21 UTC

[jira] [Commented] (OAK-1332) Large number of changes to the same node can fill observation queue

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

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

I think this is a limitation we can live with. To make it more explicit I suggest to:
* document it,
* add a (configurable?) limit for how many changes per node are covered by observation,
* drop events when the limit is exceeded and log a warning.

> Large number of changes to the same node can fill observation queue
> -------------------------------------------------------------------
>
>                 Key: OAK-1332
>                 URL: https://issues.apache.org/jira/browse/OAK-1332
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 0.16
>
>
> Changing, adding or removing a lot of (10'000s or more) direct children of node with on save() might cause observation queues to fill up. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)