Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

cq5.5 to aem 6.1 version migration

Avatar

Avatar
Validate 1
Level 2
nvssr90
Level 2

Likes

6 likes

Total Posts

22 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Ignite 5
View profile

Avatar
Validate 1
Level 2
nvssr90
Level 2

Likes

6 likes

Total Posts

22 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Ignite 5
View profile
nvssr90
Level 2

16-09-2016

Hi Guys,

We are migrating from CQ5.5 to AEM6.1 and we would like to migrate content version history from crx to oak. So, we used CRX2OAK migration tool to do this. Versions are migrated successfully but once the AEM instance is up. It keeps recreating indexes and run out of disk space. We tried couple of times but seems to be same issue every time.

We tried offline and online compaction but size seems to be same. Can you please guide us what can be tried?

 

Thanks,Sai

View Entire Topic

Avatar

Avatar
Boost 5
Employee
vmehrotr
Employee

Likes

19 likes

Total Posts

43 posts

Correct Reply

5 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Applaud 5
View profile

Avatar
Boost 5
Employee
vmehrotr
Employee

Likes

19 likes

Total Posts

43 posts

Correct Reply

5 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Applaud 5
View profile
vmehrotr
Employee

16-09-2016

Considering my previous experiences, there are a few things you could try out at your end and see how much it helps:

a) Ensure that the repository and datastore are on local disk instead of a NAS/SAN. This should increase

performance greatly.

Startup options

--mmap --early-shutdown

Above options

1) mmap - Use memory mapped io by default

2) early-shutdown - Shutdown the CRX post copying and before indexing is done to ensure that critical memory resources are freed up

b) CRX repository.xml was tweaked

1) TarPersistenceMananger change in all 3 places

2) Disabled autoOptimizeAt by setting the value to empty. This would prevent the auto optimizer to trigger during the long run

3) Set indexInMemory to true

4) Changed the bundleCacheSize to 100 MB

c) An effort was made to reduce time spent in getting full text indexing to complete. This involved pre extracting text from binaries based on new feature

https://issues.apache.org/jira/browse/OAK-2892 For more details refer to http://jackrabbit.apache.org/oak/docs/query/lucene.html#Pre-Extracting_Text_from_Binaries

This can help greatly. Steps are mentioned in the documentation.

d) There are also configurations available to fasten this process and I am looking forward to understand that do you have a requirement to enable full text indexing for pdf's

and word docs. If not, we can complete exclude them from indexing.

If your answer is YES and your concern is to reduce the upgrade process time, the config change should be done at the very start of the upgrade process as described below :

1) you can disable indexes with disable-indexes as follows :

java -Xmx4G -jar ~/Downloads/crx2oak-1.3.4-standalone.jar --mmap --copy-orphaned-versions=flase --copy-versions=false --disable-indexes=lucene crx-quickstart/repository newrepo/

2) Once the content migration is done, unpack aem-quickstart-6.1.0.jar as follows.

java -jar ../aem-quickstart-6.1.0.jar -unpack

Then, create an install folder (crx-quickstart/install) and deploy lucene-index-config.zip to the install folder.

The config file is here - https://files.acrobat.com/a/preview/e47bccf6-56c4-41b9-8b79-1d911b5ddb15

It contains the definition of the lucene index with the right tika config.

Please note that if you disable an index during upgrade, it will not appear in the AEM anymore. Therefore the package contains all the OOTB indexes together with the tika configuration.