Hi,
We have an AEM 6.1 running with multiple websites and every night we run tar compaction. When tar compaction finishes we often get SegmentNotFound exceptions in our log file and have to roll back (manually by changing the journal.log).
When I roll back the changes AEM starts reindexing the /oak:index/ entries and takes hours to start.
What could cause the segment not found exceptions after tar compaction?
And how do I have to change the /oak:index/ entries to make sure that the startup time does not take hours?
Kind regards
Steven
Views
Replies
Total Likes
Hi Steve,
in any case: Please raise a Daycare ticket!
Furtheron: What Oak version do you use? And what kind of "tar compaction" do you run, online or offline?
Kind regards,
Jörg
Views
Replies
Total Likes
Hi,
I logged a daycare ticket and hope they will have a look soon, at the moment the indexes on startup are really causing issues on our production system.
We are using AEM 6.1 with oak version Oak 1.2.11 (we installed Hotfix 7700) We are using offline tar compaction, that runs at night.
Kind regards
Steven
Views
Replies
Total Likes
Hi Steven,
Did you get any response to your ticket?
Thank you!
Kind regards,
Norbert
Views
Replies
Total Likes