Analyze unusual repository growth

Problem

Cause

Many things can cause unusual increases in disk utilization. Some potential causes:

Proper maintenance hasn't been run on the system. See this article for details on various system maintenance activities.

AEM or the application is creating very large number of nodes or updates to node properties. This could be due to a misconfiguration or an application code bug. Since the tar storage in Oak operates in an append-only mode, repeated saving of nodes further contributes to excessive repository growth.

Very large file(s) have been uploaded to AEM Assets or package manager.

Debug or Trace logging was left enabled.

Analysis / Resolution

A. If AEM is running and there is ample disk space

1. Configure Oak write trace logging

If AEM is still running then we can enable a debug logger to tell us which repository paths are being written to. To enable this logger, install the attached log configuration package below or follow these steps:

This Package contains the required configuration for the logging write session for oak. Install this package via the CRX Package Manager. After your monitor period please make sure to uninstall the package.

Výstraha:

The log includes information regarding all writes and session details. If you use this logger then make sure you have sufficient disk space.

Uninstall the log configuration package or remove the log configuration after a short period of having this enabled to avoid further disk space consumption.

2. Run the disk usage report

You can also leverage the Disk Usage report http://host:port/etc/reports/diskusage.html.This report displays the disk space used by repository path. The report is drillable, allowing you to view subtrees as well.

3. Capture thread dumps and perform profiling

After using the repgrowth.log to get some idea of what data is being written, we can get information about what code is writing that data by capturing thread dumps and running CPU profiling.