Compaction Skipped Large Container Volume Alarm
Compaction is skipped due to large container with garbage below the garbage threshold in the container.
- Label for Alarm on MCS UI
-
Compaction Skipped Large Container
- Text for Alarm on Log File
-
VOLUME_ALARM_COMPACTION_SKIPPED_LARGE_CONTAINER
- Meaning
-
Compaction has been skipped for the container because container size is large, but the amount of garbage to be reclaimed from the container is not large enough. When the amount of garbage to reclaim is less than the value specified for
mastgateway.ctc.opt.largenuminodes.threshmb
(default is 2GB), compaction is skipped. Refer to Data Compaction and Recall Criteria for details on data compaction and recall criteria.Compaction is skipped for some large containers having garbage beyond configured threshold. This happens when the value of the configuration variable,
mastgateway.ctc.opt.largenuminodes.skipqualifiedctrs.enabled
, is set to 1.NOTERefer to config for the detailed description of the configuration variables. - Resolution
-
Use one of the following ways as suitable.
- Increase the garbage threshold high enough so that when compaction
runs, the actual amount of garbage goes below this higher threshold.
The variable,
mastgateway.ctc.opt.largenuminodes.threshmb
, represents the garbage threshold. - Run compaction manually with a lower overhead threshold. This causes
compactor to free up more space. However, this option causes
compaction to run longer. Default overhead threshold is 30%. Refer
to Running the Compactor Using the CLI and REST API for details on running
compaction manually.
The alarm goes away when compaction frees up enough space in the container. The alarm continues to display if the garbage in the container after compaction is above the garbage threshold.
- Increase the garbage threshold high enough so that when compaction
runs, the actual amount of garbage goes below this higher threshold.
The variable,