[
https://issues.apache.org/jira/browse/OAK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562923#comment-14562923
]
Chetan Mehrotra commented on OAK-2927:
--------------------------------------
Given that {{newIds}} is used to handle moves and is applicable when there is
an incremental index update. In case of a reindex all index entries would only
be for newly added node and there would not be any deleted node. Thus for
migration usecase we can rely on fact that it would be a case of reindex and
then editor need not keep a record of {{newIds}} and avoid consuming all that
memory
/cc [~alex.parvulescu]
> ReferenceEditor newIds cosuming lots of memory during migration
> ---------------------------------------------------------------
>
> Key: OAK-2927
> URL: https://issues.apache.org/jira/browse/OAK-2927
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.3.0, 1.2.3, 1.0.15
>
>
> In a large migration its seen that {{ReferenceEditor}} {{newIds}} can consume
> lots of memory as it records all the uuid property. This system has 33
> million uuid index and the set was consuming ~1.5G of memory
> We should look into ways such that it does not have to maintain such a big in
> memory state
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
