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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/03/21 13:33:38 UTC

[jira] [Created] (OAK-2663) Unique property index can trigger OOM during upgrade of large repository

Chetan Mehrotra created OAK-2663:
------------------------------------

             Summary: Unique property index can trigger OOM during upgrade of large repository
                 Key: OAK-2663
                 URL: https://issues.apache.org/jira/browse/OAK-2663
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: upgrade
            Reporter: Chetan Mehrotra
            Assignee: Chetan Mehrotra


{{PropertyIndexEditor}} when configured for unique index maintains an in memory state of indexed property in {{keysToCheckForUniqueness}}. This set would accumulate all the unique values being indexed.

In case of upgrade where the complete upgrade is performed in single commit this state can become very large. Further later while exiting the editor validates that all such values are actually unique by iterating over all such values.

We should look into other possible ways to enforce uniqueness constraint



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