Dear experts,
I have online TarMK compaction configured and sometimes it does get rid of stuff, but mostly it announces a lot:
org.apache.jackrabbit.oak.plugins.segment.file.FileStore Estimated compaction in 11.69 min, gain is 12% (31013621760/35640866304) or (31.0 GB/35.6 GB), so running compaction
91383:29.01.2016 02:11:41.848 *INFO* [TarMK compaction thread [/opt/database/www/apps/publish/crx-quickstart/repository/segmentstore], active since Fri Jan 29 02:00:00 MET 2016, previous max duration 4738653ms] org.apache.jackrabbit.oak.plugins.segment.file.FileStore TarMK compaction running, strategy=DefaultCompactionStrategy [pauseCompaction=false, cloneBinaries=false, cleanup=CLEAN_OLD, olderThan=36000000]
But in the end it reclaims zero. I tried changing olderThan parameter over JMX to 3600 and also changing CLEAN_OLD to CLEAN_ALL, but it did not help.
Is there a way to give the compactor more courage to remove garbage?
Kind regards,
Ivan
Views
Replies
Total Likes
HI Ivan,
From which JMX config you changed the value?
Views
Replies
Total Likes
HI Ivan,
Have you tried earlier with offline compaction?
If not, for the first time , run offline compaction and carry forward you can have use of online compaction
Views
Replies
Total Likes
This one:
org.apache.jackrabbit.oak: "Segment node store compaction strategy settings" ("CompactionStrategy")
Views
Replies
Total Likes
Can you try offline compaction>?
Views
Replies
Total Likes
Online compaction is not as fast as offline compaction to clear the data. If we run online compaction , you are not able to see impact on disk space immediately.
If Offline compaction is running fine , then configure online compaction. Minimum 10 hours should be require the purge the values from stores for online compaction script...
Views
Replies
Total Likes
Thank you a lot for you answers!
Yes, I read once that online compaction is slower. The strange thing is, after a minute of compaction there is a message in the log "TarMK revision cleanup completed". Does the script continue running afterwards?
Views
Replies
Total Likes
yes. please wait and debug in log
Views
Replies
Total Likes
Did that work for you?
Views
Replies
Total Likes
I'm sorry, but the repo just keeps growing.
I think, the compactor reclaims a little, but the newly produced garbage overtrumps all the progress. So, overall the size increases steadily.
Views
Replies
Total Likes
What is the use case for your AEM instance? Are you uploading a lot of assets?
Can you confirm what happened to the repository size when you ran offline compaction?
Regards,
Opkar
Views
Replies
Total Likes
Sorry for the delay.
You are right, there is a lot of asset uploading going on and some regular site changes.
Offline compaction reduces the size by more than 50 percent.
Since 19. February there is a hotfix available to update oak to 1.2.11. Maybe it will get better after update?
Kind regards,
Ivan
Views
Replies
Total Likes
Views
Likes
Replies