[
https://issues.apache.org/jira/browse/OAK-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371376#comment-14371376
]
Chetan Mehrotra commented on OAK-2657:
--------------------------------------
bq. I still think this frees an important amount of memory for the indexers so
it is interesting to add it in
Yes thats a good case for such an approach
bq. maybe put it behind some sort of a flag ("earlyShutdown") so people can use
it out without losing the existing behavior
That can be done. However current RepositoryUpgrade does not have a flag
support. With OAK-2586 [~jsedding] provided a patch which introduces the
builder approach to construct RepositoryUpgrade instance. May be we at least
incorporate that for now to expose such a flag
> Repository Upgrade could shut down the source repository early
> --------------------------------------------------------------
>
> Key: OAK-2657
> URL: https://issues.apache.org/jira/browse/OAK-2657
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Reporter: Alex Parvulescu
> Attachments: OAK-2657.patch
>
>
> I noticed that during the upgrade we can distinguish 2 phases: first copying
> the data from the source, then applying all the Editors (indexes and co.).
> After phase 1 is done the repository upgrader could shut down the old repo to
> allow clearing some memory resources which might be used for the second phase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
