Automatic disk resizes
Overutilizing storage on a Postgres server can be operationally dangerous because there might not be enough disk space for the server to recover in case of an emergency.
To prevent such situations, Crunchy Bridge will take actions to resize your server's disk size on your behalf. Here is a timeline of the actions that are taken as a server's disk usage grows beyond 75%:
- 75% disk used: warn team administrators by email
- 80% disk used: warn team administrators by email
- 85% disk used: warn team administrators by email
- 90% disk used: trigger an automatic disk resize; notify team administrators by email
When an automatic resize is triggered, the new size is calculated based on the original size.
- Disks smaller than 1 TB will be increased by 25% (e.g. 100 GB becomes 125 GB).
- Disks larger than 1 TB will be increased by 15% (e.g. 1000 GB becomes 1150 GB).
Like our High Availability feature, the Bridge system will bring up a new machine behind the scenes, copy your data, and execute a failover. You should ensure your application is set up to automatically reconnect to the database since there will be a brief service interruption (no more than a few minutes). You can read more about this process on the Cluster Management page.
You can trigger a manual resize by selecting "Resize" from a cluster's "Cluster Actions" menu. For details on how manual resize operates, see the Cluster resize section of the Cluster Management page.
Although Crunchy Bridge will automatically resize cluster disks for you, we strongly encourage team admins to heed the disk size warning emails and take action in advance of an automatic resize.
If you initiate a manual resize once the disk is above the 75% threshold, the system will automatically resize it by 15% or 25%, as outlined above.
Please reach out to support if you plan to initiate a resize but need finer control over the increase.