AEM6 with SP1 repository compacting (TarMK) doesn't work | Community
Skip to main content
M
Marek_Krokosins
Level 2
October 16, 2015
Solved

AEM6 with SP1 repository compacting (TarMK) doesn't work

  • October 16, 2015
  • 3 replies
  • 1149 views

Hi.

 

I have installed service pack 1 on fresh AEM6 instance. I also checked if the oak version is correct, and it was 1.0.5, I have deployed my packages few times and repository size growth up to ~9 GB. I tried to fire compacting from the JMX console (/system/console/JMX -> RepositoryManagment) but it didn't compact the repository size. In logs I have information, that compacting has been paused, and probably this is the reason why it didn't worked. I also read that just one time I should fire the offline oak compacting tool, so I did that, and repository size has backed to normal. Once again I deployed my package few times, repository size was again around ~5GB. Once again I tried to fire compacting from JMX, but it didn't helped. What I have in logs:

18.09.2014 09:32:45.466 *INFO* [TarMK compaction thread [path\crx-quickstart\repository\segmentstore], active since Thu Sep 18 09:32:45 CEST 2014, previous max duration 3195ms] org.apache.jackrabbit.oak.plugins.segment.file.FileStore TarMK compaction started 18.09.2014 09:32:47.967 *INFO* [TarMK compaction thread [path\crx-quickstart\repository\segmentstore], active since Thu Sep 18 09:32:45 CEST 2014, previous max duration 3195ms] org.apache.jackrabbit.oak.plugins.segment.file.FileStore Estimated compaction in 2501ms, gain is 39% (2932442624/4838666752), so running compaction 18.09.2014 09:32:47.967 *INFO* [TarMK compaction thread [path\crx-quickstart\repository\segmentstore], active since Thu Sep 18 09:32:45 CEST 2014, previous max duration 3195ms] org.apache.jackrabbit.oak.plugins.segment.file.FileStore TarMK compaction paused 18.09.2014 09:32:49.669 *INFO* [TarMK flush thread [path\crx-quickstart\repository\segmentstore], active since Thu Sep 18 09:32:49 CEST 2014, previous max duration 1783ms] org.apache.jackrabbit.oak.plugins.segment.file.FileStore TarMK revision cleanup started 18.09.2014 09:32:50.319 *INFO* [TarMK flush thread [path\crx-quickstart\repository\segmentstore], active since Thu Sep 18 09:32:49 CEST 2014, previous max duration 1783ms] org.apache.jackrabbit.oak.plugins.segment.file.FileStore TarMK revision cleanup completed in 649ms

I also tried to compact data using instructions in http://docs.adobe.com/docs/en/aem/6-0/deploy/upgrade/microkernels-in-aem-6-0.html

Probably I'm doing something wrong, the question is what is it?

 

Best Regards.

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 Sham_HC

Micro-BIOS wrote...

The only way I have found till now to compact the repository is to turn off the AEM instance and run oak-run. I'm convinced that AEM should be still in beta.

Hi,

    There are some edge cases it can happen, hence requesting to file daycare so that we can investigate and provide solution to meet your timelines. Also we understand the risk & hence to track down need official ticket. 

Thanks,

Sham

3 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

Please file a daycare ticket. 

A
Anonymous
October 16, 2015

The only way I have found till now to compact the repository is to turn off the AEM instance and run oak-run. I'm convinced that AEM should be still in beta.

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Micro-BIOS wrote...

The only way I have found till now to compact the repository is to turn off the AEM instance and run oak-run. I'm convinced that AEM should be still in beta.

Hi,

    There are some edge cases it can happen, hence requesting to file daycare so that we can investigate and provide solution to meet your timelines. Also we understand the risk & hence to track down need official ticket. 

Thanks,

Sham

Terms & ConditionsAccessibility statement

Loading footer...