TarMK compaction thread is not getting stopped at the scheduled windowEndTime | Community
Skip to main content
gowrishankarp21
Level 2
April 26, 2016
Solved

TarMK compaction thread is not getting stopped at the scheduled windowEndTime

  • April 26, 2016
  • 4 replies
  • 1366 views

We are using the default daily maintenance window 2.00 to 5.00 configured at /libs/granite/operations/config/maintenance/granite:daily

TarMK compaction thread is getting started at the scheduled start time of 2.00 AM, but it is not getting stopped at 5.00 and it is running till it gets completed( The complete run takes around 7 to 12 hours). 

Also if we try to stop the server at that time (when TarMK compaction is running), the stop process is waiting for the TarMK compaction to get completed. we need to kill that process to get it stopped, otherwise we need to wait for the TarMK compaction to get complete.

kindly help me on this.

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 smacdonald2008

I checked with Support on this issue - this was the response: 

This is one of the possible issues one can run into with “Online Compaction” which is not recommended for AEM 6.0 & 6.1.

For AEM 6.2 (though not likely the case for this customer), we have restricted support for online compaction (subject to evaluation on case by case basis by support & engineering team).

Online Compaction is turned off by default on AEM 6.1 & 6.2. Offline Compaction as documented at [1] is the recommended approach:

https://docs.adobe.com/docs/en/aem/6-0/deploy/upgrade/microkernels-in-aem-6-0.html#Maintaining the Repository

4 replies

smacdonald2008
Level 10
April 26, 2016

HAve you read these AEM topics: 

https://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys/tarmk-cold-standby.html

http://www.aemcq5tutorials.com/tutorials/tarmk-cold-standby-aem-6/

These are the only topics I know on this subject. If they are not helpful , let me know. 

smacdonald2008
smacdonald2008Accepted solution
Level 10
April 26, 2016

I checked with Support on this issue - this was the response: 

This is one of the possible issues one can run into with “Online Compaction” which is not recommended for AEM 6.0 & 6.1.

For AEM 6.2 (though not likely the case for this customer), we have restricted support for online compaction (subject to evaluation on case by case basis by support & engineering team).

Online Compaction is turned off by default on AEM 6.1 & 6.2. Offline Compaction as documented at [1] is the recommended approach:

https://docs.adobe.com/docs/en/aem/6-0/deploy/upgrade/microkernels-in-aem-6-0.html#Maintaining the Repository

AnkurAhlawat-1
Level 6
April 26, 2016
  This is a known issue, I too faced the same problem that online tar running for around 6-8 hours and if you try to kill process frequently then it will corrupt your repository too. That why we have started offline compaction as it took around 30 min for us and recommended from adobe too. Another drawback of online compaction was it reduced the performance of author instance very much till tar optimision is running.
gowrishankarp21
Level 2
April 27, 2016

Thanks McDonald and Ankur ..