Managing Software Event Broker Storage

The software event broker uses PubSub+ specific constructs called storage-elements to store state information. These storage-elements allow you to customize the event broker storage resources to meet the needs of your application.

For assistance with planning and optimizing the storage configuration of your deployment, contact Solace Support.

Understanding Storage-Elements

The event broker maintains a significant amount of state on disk, including spooled messages, runtime configuration, and diagnostic information. This state is organized into directories called storage-elements.

These storage-elements are portable—that is, you can map a storage-element to any storage device that meets the capacity, persistence, and performance requirements of the application. Each storage-element is independently monitored and managed by the event broker.

The amount of disk space needed for each storage-element depends on the event broker configuration. See Modifying System Limits Using System Scaling Parameters for more information.

We recommend that you map storage-elements to external storage. For more information, see Managing Storage for Container Images and Managing Storage for Virtual Machine Images.

There are six storage-elements, as described in the table below.

Storage-Element Properties

Storage-Element

Use Device Considerations Mounted On
jail Stores logs and configuration database backups Depending on the level of broker activity, the write load of this storage-element can be moderate to high. The contents of this storage-element are not necessary during upgrade but are helpful in the event support is required. /usr/sw/jail
var Stores the configuration database. Typically, the write load of this storage-element is low, however, poor device throughput can lead to system instability. The contents of this storage-element must be preserved during upgrades. /usr/sw/var
diagnostics Storage for diagnostic information for support. The contents of this storage-element are not necessary during upgrade but are helpful in the event support is required. /var/lib/solace/diags
spool Stores spooled messages. Broker stability and performance is directly related to device performance. The contents of this storage-element must be preserved during upgrades to prevent message loss. /usr/sw/internalSpool
adb Stores undelivered messages. Broker stability and performance is directly related to device performance. /usr/sw/internalSpool/softAdb
adbBackup Stores runtime information used for recovery after system shutdown. The contents of this storage-element are not necessary during upgrade but are helpful in the event support is required. /usr/sw/adb