How to clean ...\crx-quickstart\repository\segmentstore

[Reini-]

Hi,

I installed AEM6.0 on our test environment. After a few days the disk is full, because ....\crx-quickstart\repository\segmentstore needs more than 20GB, although we didn't add new content, ....

Can anybody tell me, how to clean crx-quickstart\repository\segmentstore? The startTarOptimization() job (http://localhost:4502/system/console/jmx/com.adobe.granite%3Atype%3DRepository) doesn't work, because I get the error "javax.jcr.UnsupportedRepositoryOperationException".

regards

Reinhard

[miqk]

I have the same problem.  Its odd that a new release of CQ6 would have a bug to cause the disk to be full after some days.

[Reini-]

Hi,

as the adobe support told me, this is known oak bug. So the repository size grows every hour. In my opion AEM6.0 is only usable for testing at the moment, but not for real projects.

regards

Reini

[askdctm]

Hi Reinhard/Michael,

Have few doubts as below:

In AEM 5.6.1, on my OOTB local instance , under the path 

C:\cq5\author\crx-quickstart\repository , there is nothing by name \segmentstore  present.

1] Is it a new feature present in AEM 6.0? Is it something like a data store?

2] Also, what exactly does this segment store contain and what is the use of it?

 @Reinhard

1] I guess TarOptimization and Data store GC are different from each other. Probably startTarOptimization() job  will not take of segment store [myself assuming that it is similar to data store]

Any thoughts would be helpful, because we are also planning to introduce 6.0, in our environments.

If there is any important additional information , you could share on the installation/upgrade to 6.0 , would be helpful.

[Sham_HC]

Reini- wrote...

as the adobe support told me, this is known oak bug. So the repository size grows every hour. In my opion AEM6.0 is only usable for testing at the moment, but not for real projects.

Agree it is bug & soon will be addressed. But should not block from going live on real projects. Please ask support engineer to share tool to compact an existing TarMK deployment till hotfix is released.  If tool is not acceptable update ticket with business impact & project schedule will help you out.