Vertica Analytics Platform Version 9.2.x Documentation

Managing Disk Space

Vertica detects and reports low disk space conditions in the log file so you can address the issue before serious problems occur. It also detects and reports low disk space conditions via SNMP traps if enabled.

Critical disk space issues are reported sooner than other issues. For example, running out of catalog space is fatal; therefore, Vertica reports the condition earlier than less critical conditions. To avoid database corruption when the disk space falls beyond a certain threshold, Vertica begins to reject transactions that update the catalog or data.

A low disk space report indicates one or more hosts are running low on disk space or have a failing disk. It is imperative to add more disk space (or replace a failing disk) as soon as possible.

When Vertica reports a low disk space condition, use the DISK_RESOURCE_REJECTIONS system table to determine the types of disk space requests that are being rejected and the hosts on which they are being rejected.

To add disk space, see Adding Disk Space to a Node. To replace a failed disk, see Replacing Failed Disks.

Monitoring Disk Space Usage

You can use these system tables to monitor disk space usage on your cluster:

System table Description
DISK_STORAGE

Monitors the amount of disk storage used by the database on each node.

COLUMN_STORAGE

Monitors the amount of disk storage used by each column of each projection on each node.

PROJECTION_STORAGE

Monitors the amount of disk storage used by each projection on each node.

In This Section