Skip to content

Commit 220e79f

Browse files
committed
Compute start stop update
1 parent 6c51b91 commit 220e79f

File tree

3 files changed

+77
-6
lines changed

3 files changed

+77
-6
lines changed
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Start and stop cluster compute - Azure Cosmos DB for PostgreSQL
3+
description: Learn about how to start and stop compute on the cluster nodes
4+
ms.author: nlarin
5+
author: niklarin-msft
6+
ms.service: cosmos-db
7+
ms.subservice: postgresql
8+
ms.topic: concept
9+
ms.date: 3/22/2023
10+
---
11+
# Start and stop compute on cluster nodes
12+
13+
[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
14+
15+
Azure Cosmos DB for PostgreSQL allows to stop compute on all nodes in a cluster. Compute billing is paused when cluster is stopped and continues when computer is started again.
16+
17+
> [!NOTE]
18+
> Billing for provisioned storage on all cluster nodes continues when cluster's compute is stopped.
19+
20+
You can stop compute on a cluser for as long as you need.
21+
22+
You can perform management operations such as compute or storage scaling, adding a worker node, or updating networking settings only on clusters with started compute.
23+
24+
If cluster has [high availablity (HA)](./concepts-high-availability.md) enabled, compute start and stop operations would start and stop compute on all primary and standby nodes in the cluster.
25+
26+
You can start and stop compute on the primary cluster and its [read replicas](./concepts-read-replicas.md) independently.
27+
28+
## Next steps
29+
30+
- Learn how to start and stop [cluster compute in Azure Cosmos DB for PostgreSQL](./how-to-start-stop-cluster.md)
31+
- Learn about [pricing options in Azure Cosmos DB for PostgreSQL](./resources-pricing.md)
32+
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Start and stop cluster - Azure Cosmos DB for PostgreSQL
3+
description: How to start and stop compute on the cluster nodes
4+
ms.author: nlarin
5+
author: niklarin-msft
6+
ms.service: cosmos-db
7+
ms.subservice: postgresql
8+
ms.topic: how-to
9+
ms.date: 3/03/2023
10+
---
11+
# Start and stop compute on a cluster
12+
13+
[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
14+
15+
Azure Cosmos DB for PostgreSQL provides an ability to stop and start compute on all nodes in a cluster.
16+
17+
## Stop a running cluster
18+
19+
1. In the [Azure portal](https://portal.azure.com/), choose the Azure Cosmos DB for PostgreSQL cluster that you want to stop.
20+
21+
2. From the **Overview** page, click the **Stop** button in the toolbar.
22+
23+
> [!NOTE]
24+
> Once the cluster is stopped, other management operations are not available for the cluster.
25+
26+
27+
## Start a stopped cluster
28+
29+
1. In the [Azure portal](https://portal.azure.com/), choose the Azure Cosmos DB for PostgreSQL cluster that you want to start.
30+
31+
2. From the **Overview** page, click the **Start** button in the toolbar.
32+
33+
> [!NOTE]
34+
> Once the cluster is started, all management operations are now available for the cluster.
35+
36+
## Next steps
37+
38+
- Learn more about [compute start and stop in Azure Cosmos DB for PostgreSQL](./concepts-compute-start-stop.md).
39+

articles/cosmos-db/postgresql/product-updates.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Product updates for Azure Cosmos DB for PostgreSQL
3-
description: New features and features in preview
3+
description: Release notes, new features and features in preview
44
ms.author: jonels
55
author: jonels-msft
66
ms.custom: mvc
77
ms.service: cosmos-db
88
ms.subservice: postgresql
99
ms.topic: conceptual
10-
ms.date: 02/25/2023
10+
ms.date: 03/23/2023
1111
---
1212

1313
# Product updates for Azure Cosmos DB for PostgreSQL
@@ -22,14 +22,14 @@ Updates that don’t directly affect the internals of a cluster are rolled out g
2222

2323
Updates that change cluster internals, such as installing a [new minor PostgreSQL version](https://www.postgresql.org/developer/roadmap/), are delivered to existing clusters as part of the next [scheduled maintenance](concepts-maintenance.md) event. Such updates are available immediately to newly created clusters.
2424

25+
### March 2023
26+
27+
* General availability: Cluster compute [start / stop functionality](./concepts-compute-start-stop.md) is now supported across all configurations.
28+
2529
### February 2023
2630

2731
* General availability: 4 TiB, 8 TiB, and 16 TiB storage per node is now supported for [multi-node configurations](resources-compute.md#multi-node-cluster) in addition to previously supported 0.5 TiB, 1 TiB, and 2 TiB storage sizes.
2832
* See cost details for your region in 'Multi-node' section of [the Azure Cosmos DB for PostgreSQL pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/postgresql/).
29-
* General availability: [Latest minor PostgreSQL version updates](reference-versions.md#postgresql-versions) (11.19, 12.14, 13.10, 14.7, and 15.2) are now available in all supported regions.
30-
* Existing clusters will get minor Postgres version update with [the next maintenance](concepts-maintenance.md)
31-
* Major Postgres and minor Citus [version upgrades](concepts-upgrade.md) can be performed in-place.
32-
3333

3434
### January 2023
3535

0 commit comments

Comments
 (0)