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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Tar PM online compaction AEM 6.1

samthadhani
Level 3
Level 3

Hi,

I have been working on Tar optimization on AEM 6.1. I remember from 5.6.1 that there was a setting in some xml (repository.xml or workspace.xml ) where you would set time between which every night the Tar optimization would run? Is that still relevant?

In the newest documentation about 6.1 , i think there is just a flag (pauseCompaction) that needs to be set to false. Now, I have set this flag to be false in the sling:OsgiConfig which is deployed with /apps in the project and within the install directory in crx-quickstart/install/org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService.config there is no entry of pauseCompaction. Would the tar compaction still happen overnight?

Also, what takes precedence settings in /apps or one that are loaded from crx-quickstart/install directory?

/crx-quickstart/install/org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService.cfg

pauseCompaction=false 

Finally, do we need to do anything for fileDataStorage?

Cheers

1 Accepted Solution
kunal23
Correct answer by
Level 10
Level 10
  1. Tar PM online compaction job in 6.1 is scheduled to run between 2:00 to 5:00 hours on daily basis. You can check the status of the last run and next run on the maintenance dashboard - http://localhost:4502/libs/granite/operations/content/maintenance/window.html/mnt/overlay/granite/o.... Also, if you want to see the configuration of the schedule in crxde then check the properties of the following node - /libs/granite/operations/config/maintenance/granite:daily 
     
  2. The precedence of osgi:config is followed as per below order- 
       1. Repository nodes under /apps/*/config....either with type sling:OsgiConfig or property files (CHECK)
       2. Repository nodes with type sling:OsgiConfig under /libs/*/config.... (ootb defns)
       3. Any .config files from <cq-installation-dir>/crx-quickstart/launchpad/config/.... on the local file system.
     
  3. If you are using external data store then you need to schedule the data store garbage collection job as it is not auto scheduled as Tar compaction. See the following link - https://docs.adobe.com/docs/en/aem/6-1/administer/operations/data-store-garbage-collection.html 

View solution in original post

3 Replies
kunal23
Correct answer by
Level 10
Level 10
  1. Tar PM online compaction job in 6.1 is scheduled to run between 2:00 to 5:00 hours on daily basis. You can check the status of the last run and next run on the maintenance dashboard - http://localhost:4502/libs/granite/operations/content/maintenance/window.html/mnt/overlay/granite/o.... Also, if you want to see the configuration of the schedule in crxde then check the properties of the following node - /libs/granite/operations/config/maintenance/granite:daily 
     
  2. The precedence of osgi:config is followed as per below order- 
       1. Repository nodes under /apps/*/config....either with type sling:OsgiConfig or property files (CHECK)
       2. Repository nodes with type sling:OsgiConfig under /libs/*/config.... (ootb defns)
       3. Any .config files from <cq-installation-dir>/crx-quickstart/launchpad/config/.... on the local file system.
     
  3. If you are using external data store then you need to schedule the data store garbage collection job as it is not auto scheduled as Tar compaction. See the following link - https://docs.adobe.com/docs/en/aem/6-1/administer/operations/data-store-garbage-collection.html 

View solution in original post

kautuk_sahni
Community Manager
Community Manager

Hi 

There is a knowledge Base article on Tar PM Optimization,

Link:- https://helpx.adobe.com/experience-manager/kb/TarPMOptimization.html

I hope this would help you.

Thanks and Regards

Kautuk Sahni