File tree Expand file tree Collapse file tree 1 file changed +5
-4
lines changed Expand file tree Collapse file tree 1 file changed +5
-4
lines changed Original file line number Diff line number Diff line change @@ -15,8 +15,9 @@ scaling to deal with increased load. The Azure portal makes it easy to either
15
15
add new worker nodes or increase existing nodes’ memory, disk, and CPU
16
16
capacity.
17
17
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.
20
21
21
22
![ Resource sliders] ( ./media/howto-hyperscale-scaling/01-sliders-workers.png )
22
23
@@ -29,8 +30,8 @@ PostgreSQL server group. Adjust the sliders to change the values:
29
30
> interface. Doing so also requires opening a support ticket.
30
31
31
32
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,
34
35
connect to the cluster coordinator node with psql and run:
35
36
36
37
``` sql
You can’t perform that action at this time.
0 commit comments