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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/11/10 09:35:59 UTC

[jira] [Updated] (OAK-4065) Counter index can get out of sync

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

Julian Reschke updated OAK-4065:
--------------------------------
    Fix Version/s: 1.6

> Counter index can get out of sync
> ---------------------------------
>
>                 Key: OAK-4065
>                 URL: https://issues.apache.org/jira/browse/OAK-4065
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.6, 1.5.0
>
>         Attachments: OAK-4065-b.patch, OAK-4065.patch, probability_1m_10times-add1remove1m.png
>
>
> I don't have a reproducible test case yet, but it looks like some usage pattern  (for example creating, deleting, moving many nodes in one transaction) can cause the counter index to get out of sync with the real data. Worst case, the counter index thinks that the repository is empty (the root node has no descendent nodes).
> I want to write test cases to find the problem, or to prove that it doesn't get out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)