Skip to content

Commit cc483dd

Browse files
committed
Update link hash
1 parent 5837197 commit cc483dd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/postgresql/howto-hyperscale-alert-on-metric.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: jonels-msft
55
ms.author: jonels
66
ms.service: postgresql
77
ms.topic: conceptual
8-
ms.date: 2/18/2020
8+
ms.date: 3/16/2020
99
---
1010

1111
# Use the Azure portal to set up alerts on metrics for Azure Database for PostgreSQL - Hyperscale (Citus)
@@ -96,7 +96,7 @@ As the disk approaches its space limit, try these techniques to get more free sp
9696

9797
* Review data retention policy. Move older data to cold storage if feasible.
9898
* Consider [adding nodes](howto-hyperscale-scaling.md#add-worker-nodes) to the server group and rebalancing shards. Rebalancing distributes the data across more computers.
99-
* Consider [growing the capacity](howto-hyperscale-scaling.md#increase-vcores) of worker nodes. Each worker can have up to 2 TiB of storage. However adding nodes should be attempted before resizing nodes because adding nodes completes faster.
99+
* Consider [growing the capacity](howto-hyperscale-scaling.md#increase-or-decrease-vcores-on-nodes) of worker nodes. Each worker can have up to 2 TiB of storage. However adding nodes should be attempted before resizing nodes because adding nodes completes faster.
100100

101101
### CPU usage
102102

0 commit comments

Comments
 (0)