Skip to content

Commit f14439f

Browse files
committed
Flow
1 parent a7b7257 commit f14439f

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/postgresql/howto-hyperscale-scaling.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,9 @@ scaling to deal with increased load. The Azure portal makes it easy to either
1515
add new worker nodes or increase existing nodes’ memory, disk, and CPU
1616
capacity.
1717

18-
To scale worker nodes, go to the **Configure** tab in your Azure Database for
19-
PostgreSQL server group. Adjust the sliders to change the values:
18+
To increase the number of worker nodes, go to the **Configure** tab in your
19+
Hyperscale (Citus) server group. Drag the slider for **Worker node count** to
20+
change the value.
2021

2122
![Resource sliders](./media/howto-hyperscale-scaling/01-sliders-workers.png)
2223

@@ -29,8 +30,8 @@ PostgreSQL server group. Adjust the sliders to change the values:
2930
> interface. Doing so also requires opening a support ticket.
3031
3132
To take advantage of newly added nodes you must rebalance distributed table
32-
[shards](concepts-hyperscale-distributed-data.md#shards), meaning move some
33-
shards from existing nodes to the new ones. To start the shard rebalancer,
33+
[shards](concepts-hyperscale-distributed-data.md#shards), which means moving
34+
some shards from existing nodes to the new ones. To start the shard rebalancer,
3435
connect to the cluster coordinator node with psql and run:
3536

3637
```sql

0 commit comments

Comments
 (0)