How to check taroptimization scheduler is running or not in AEM linux server | Community
Skip to main content
A
Anonymous
February 19, 2016
Solved

How to check taroptimization scheduler is running or not in AEM linux server

  • February 19, 2016
  • 3 replies
  • 1033 views

Hi 

I want to check whether the tar optimization scheduler is running or not, if it is running is the job successful or not.

Thanks 

Srikanth

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gokul2011

Hi Srikanthg,

By default CQ starts TAR PM optimizing between 2 AM - 5 AM. If you need any custom TAR PM scheduler , then you can schedule your own time.

To check if it is working fine, navigate to your error.log file and search TAR PM keyword @ 2AM. 

You will get messgae as TAR PM Started 

By 5 AM , you will be able to see STOPPED keyword.

However  , if your  repository size is so large always go for customize TAR PM option

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 19, 2016

Hi 

There is an article talking about monitoring the progress of TarPM optimization :-

Link:- https://umalbhole.wordpress.com/category/adobe-experience-manager-day-cq/ (Search for "monitoring the progress").

// 

TarPM Optimization

This defragments the repository tar files.
http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#Optimizing20Files
Key Point: If optimization is stopped before it is finished completely, then the next time when it is started it will continue where it left off (it doesn’t start from the beginning)
For monitoring the progress, look out for the logs in attached file.

# Creation of OptimizeNow.tar files # Optimizing Version Tar files 15.12.2012 07:48:50.299 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.OptimizeFile Renaming C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\version\optimize.tar to C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\version\optimizeNow.tar 15.12.2012 07:48:50.308 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.file.TarFile C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\version\data_00000.tar id:0 length:4544000 append:4542976 27496725 optimize: 2048 # Optimizing Workspace Tar files 15.12.2012 07:48:50.308 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.OptimizeFile Renaming C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\workspaces\crx.default\optimize.tar to C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\workspaces\crx.default\optimizeNow.tar 15.12.2012 07:48:50.327 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.file.TarFile C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\workspaces\crx.default\data_00000.tar id:0 length:75501568 append:75500544 5281912 optimize: 3072 # Optimizing Tar Journal Tar files 15.12.2012 07:48:50.327 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.OptimizeFile Renaming C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\tarJournal\optimize.tar to C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\tarJournal\optimizeNow.tar 15.12.2012 07:48:50.329 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.file.TarFile C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\tarJournal\data_00000.tar id:0 length:70034944 append:70033920 15538562 optimize: 2048 # Optimization Finish # Deleting OptimizeNow.tar from Version 15.12.2012 07:48:58.351 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.OptimizeFile Deleting C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\version\optimizeNow.tar # Deleting OptimizeNow.tar from Workspace 15.12.2012 07:48:58.352 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.OptimizeFile Deleting C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\workspaces\crx.default\optimizeNow.tar # Deleting OptimizeNow.tar from TarJournal 15.12.2012 07:49:02.771 *INFO* [Tar PM Optimization] com.day.crx.persistence.tar.OptimizeFile Deleting C:\Users\vaio\Instances_SetUp\CQ5.5_author\crx-quickstart\repository\tarJournal\optimizeNow.tar

 

I hope this could help you.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 19, 2016

Hi 

Another Reference article:- https://docs.adobe.com/content/docs/en/crx/2-3/administering/persistence_managers.html#Optimizing20Files

//

TAR PM OPTIMIZATION CASE STUDY

In this example case study, iostat is used to monitor CPU and disk usage during the TAR optimization process. The disk is between 6% and 7% busy and the CPU is between 4% and 5% busy. The disks are doing about 100 transfers per second, which is a considerable load but does not approach their capability.

 

file

I hope this might help you.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
G
Gokul2011Accepted solution
Level 6
February 19, 2016

Hi Srikanthg,

By default CQ starts TAR PM optimizing between 2 AM - 5 AM. If you need any custom TAR PM scheduler , then you can schedule your own time.

To check if it is working fine, navigate to your error.log file and search TAR PM keyword @ 2AM. 

You will get messgae as TAR PM Started 

By 5 AM , you will be able to see STOPPED keyword.

However  , if your  repository size is so large always go for customize TAR PM option

Terms & ConditionsAccessibility statement

Loading footer...