problem cleaning segmentstore

manisha_joshi 15-10-2015


I am trying to clean the segmentstore folder from the author instance in aem 6.Getting this exception.:

Apache Jackrabbit Oak 1.0.8
Checkpoints D:\hmonline\servers\cq-author\crx-quickstart\repository\segmentstore

Exception in thread "main" java.lang.IllegalStateException
        at org.apache.jackrabbit.oak.plugins.segment.Segment.<init>(
        at org.apache.jackrabbit.oak.plugins.segment.file.FileStore.readSegment(
        at org.apache.jackrabbit.oak.plugins.segment.SegmentTracker.getSegment(S
        at org.apache.jackrabbit.oak.plugins.segment.SegmentId.getSegment(Segmen
 at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.getTemplat
        at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.getChildNo
        at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.<init>(Mem
        at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.createChil
        at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.getChildNo

Please provide some solution

Accepted Solutions (1)

Accepted Solutions (1)

Answers (4)

Answers (4)

anilkum 09-12-2015

Hi Gokul,

Cant seem to see the questions that you asked in reply to my first question (The forum seems to be behaving weird today)

So I am copying and replying from the details I received in mail:

1.Running offline or onlince compaction  [Anil] Offline. AEM is down.

2.Oak-run version. [Anil] 1.2.2 (oak-run-1.2.2.jar) AEM is 6.1. OAK is 1.2.2

3. Store Configurations  [Anil] We have the default TarMX setting. But when we ran this on a test environment it completed successfully. 25 GB was compacted to 11 G. The environment that we are running it now on had nearly 400GB of tar files. Is separately the node store and data store mandatory?

I referred the following documentation -

I read somewhere that oak-run needs maximum memory... is there a free disk space and free RAM prerequisite?



anilkum 08-12-2015

This is not an answer but related so adding my question..

I am facing issue in compacting where the tool is neither completing nor exiting with exception. I tried this on a lower environment and it executed successfully. On my production author it is used 100% of one CPU core. Is the oak-run.jar capable of utilizing more than 1 core on multicore machine?

Any pointers on how to monitor the oak-run.jar for periodic updates?

Also can the point of separating the datastore from segmentstore be explained further or links to some documentation provided?