Thank you both I re-implemented the migration with JCR api and it worked.
However, the move takes a really long time - 500ms per node or more. This is the typical save time per node in our environment, we were OK with it till now because we did not have any bulk updates. But with nearly 100,000 documents to move... Quick look in jVisualVM CPU Sampler shows that a lot of time is spent in ContentMirrorStoreStrategy - updating non-unique property indices. I suspect it's the nodetype index, because it takes up 40% of the documents in the nodes collection. Is there a way to speed up the process? Perhaps drop some unnecessary indices or delay reindexing? On Mon, Mar 6, 2017 at 4:30 AM, Davide Giannella <[email protected]> wrote: > On 03/03/2017 22:23, Vikas Saurabh wrote: > > that won't make callbacks to the various editors that > > you might be plugging in. It'd definitely be better to utilise JCR API... > > Session.save() would persist the changes. > > +1 for JCR Api. Missing Editors callback will mean that, for example, > you won't be updating your query indexes. > > D. > > > -- Alex Benenson
