Tanzu RabbitMQ for Tanzu Application Service: How to increase persistent disk size

Products

VMware Tanzu RabbitMQ

Issue/Introduction

RabbitMQ service instances reach persistent disk limits, triggering disk alarms and requiring disk size adjustments through Ops Manager. Example disk-related warnings include “disk alarm set” in the RabbitMQ Management UI or log entries indicating low available disk space..

Environment

VMware Tanzu RabbitMQ for Tanzu Application Service
Ops Manager with RabbitMQ tile installed
On-Demand or Pre-Provisioned service plan configurations
BOSH Director managing RabbitMQ VMs

Cause

The persistent disk size is controlled by the service plan configuration. When the allocated disk space is insufficient, RabbitMQ nodes cannot expand automatically. Disk capacity must be increased by updating plan configurations in the RabbitMQ tile within Ops Manager.

Resolution

The procedure differs depending on whether the environment uses On-Demand or Pre-Provisioned RabbitMQ service plans. Disk configuration changes are made within Ops Manager and take effect after redeployment.

For On-Demand RabbitMQ Service Instances

On-Demand plans define disk size in plan configuration settings.

Log in to the Ops Manager Installation Dashboard.
Select the VMware Tanzu RabbitMQ for Tanzu Application Service tile.
In the Settings tab, open On-Demand Plans or Global Settings for On-Demand Plans.
Change the Persistent Disk Type to a larger disk size (for example, from 20 GB to 50 GB). Modify the VM Type if a higher performance configuration is desired.
Click Save, then return to the Installation Dashboard. Select Review Pending Changes, and then Apply Changes to redeploy the On-Demand service broker and make the updated plan configuration available.

After redeployment:

Developers can create new service instances using the updated plan.
Existing service instances can be upgraded to use the modified configuration.

Example deployment name:
service-instance_GUID managed by rabbitmq-on-demand-broker

For Pre-Provisioned RabbitMQ Service Instances

Pre-Provisioned plans use fixed RabbitMQ clusters configured in the tile. Disk changes require cluster redeployment.

Log in to the Ops Manager Installation Dashboard.
Select the VMware Tanzu RabbitMQ for Tanzu Application Service tile.
In the Settings tab, locate Pre-Provisioned RabbitMQ Configuration.
Increase the Persistent Disk size for each configured RabbitMQ cluster (for example: preprovisioned-rabbit-cluster).
Click Save, return to the Installation Dashboard, select Review Pending Changes, and click Apply Changes to redeploy the cluster with expanded storage.

Example deployment name:
rabbitmq-service-preprovisioned_<environment>

Verification

Application-level Verification

In Apps Manager, confirm the service instance details show the updated plan and disk size.
Using the cf CLI, validate that the listed plan description reflects the new disk size.

Reference commands:
cf marketplace -s p.rabbitmq

Infrastructure-level Verification (BOSH)

Identify and validate the RabbitMQ deployment details using BOSH commands.

Identify the RabbitMQ deployment:

Reference commands:
bosh deployments | grep rabbit

View VM details and persistent disk allocations:

Reference commands:
bosh vms <deployment-name> --details

SSH into a RabbitMQ node and verify the storage size matches the new persistent disk allocation

Reference commands:

bosh ssh <vm-name> -d <deployment-name>

df -h /var/vcap/store

Additional Information

Changing the disk configuration triggers a service redeployment, which temporarily interrupts availability.
In On-Demand environments, the new disk configuration applies to new or upgraded instances only.
In Pre-Provisioned environments, all tenants sharing the cluster use the updated configuration after redeployment.

References