Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mr serverless ga #17907

Merged
merged 12 commits into from
Sep 29, 2023
1 change: 1 addition & 0 deletions src/current/_data/cloud_releases.csv
Original file line number Diff line number Diff line change
Expand Up @@ -65,3 +65,4 @@ date,sha
2023-09-08,null
2023-09-11,null
2023-09-22,null
2023-09-27,null
5 changes: 5 additions & 0 deletions src/current/_includes/releases/cloud/2023-09-27.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
## September 27, 2023

<h3 id="2023-09-27-general-changes"> General changes </h3>

- [Multi-region CockroachDB {{ site.data.products.serverless }}]({% link cockroachcloud/plan-your-cluster-serverless.md %}#multi-region-clusters) clusters are now [generally available](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/cockroachdb-feature-availability), and cross-region network charges are now accounted for in RU consumption.
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ AWS PrivateLink for CockroachDB {{ site.data.products.serverless }} is in **[lim

Amazon Web Services (AWS) PrivateLink support allows customers to establish SQL access to their clusters entirely through private AWS infrastructure, without exposure to the public internet, affording enhanced security and performance.

AWS PrivateLink is available only for multiregion CockroachDB {{ site.data.products.serverless }} clusters deployed on AWS.
AWS PrivateLink is available only for multi-region CockroachDB {{ site.data.products.serverless }} clusters deployed on AWS.

gemma-shay marked this conversation as resolved.
Show resolved Hide resolved
To configure PrivateLink, you create the AWS PrivateLink connection in your AWS account, then configure your cluster to allow connections from your private endpoint. For more information and detailed instructions, refer to[Network Authorization: AWS PrivateLink]({% link cockroachcloud/network-authorization.md %}#aws-privatelink).

Expand Down
4 changes: 2 additions & 2 deletions src/current/cockroachcloud/create-a-serverless-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,12 @@ For optimal performance, select the cloud provider and region nearest to where y
To create a multi-region cluster, click **Add regions** and select additional regions. A cluster can have at most six regions.

{{site.data.alerts.callout_info}}
**Multi-region for CockroachDB {{ site.data.products.serverless }} is in [preview](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/cockroachdb-feature-availability)** and subject to change. You cannot currently add or remove regions once a cluster has been created. To share feedback and/or issues, contact [Support](https://support.cockroachlabs.com/).
You cannot currently remove regions once they have been added.
{{site.data.alerts.end}}

After creating a multi-region cluster deployed on AWS, you can optionally [set up AWS PrivateLink (Limited Access)]({% link cockroachcloud/network-authorization.md %}#aws-privatelink) so that incoming connections to your cluster from applications or services running in your AWS account flow over private AWS network infrastructure rather than the public internet.

Private connectivity is not available for {{ site.data.products.serverless-plan }} clusters on GCP.
Private connectivity is not available for {{ site.data.products.serverless }} clusters on GCP.

## Step 4. Set resource limits

Expand Down
13 changes: 7 additions & 6 deletions src/current/cockroachcloud/plan-your-cluster-serverless.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,14 +48,10 @@ Each [Org Administrator]({% link cockroachcloud/authorization.md %}#org-administ

## Multi-region clusters

{{site.data.alerts.callout_info}}
{% include feature-phases/preview.md %}
{{site.data.alerts.end}}

You can [create a CockroachDB {{ site.data.products.serverless }} cluster]({% link cockroachcloud/create-a-serverless-cluster.md %}) with up to [six regions]({% link cockroachcloud/serverless-faqs.md %}#what-regions-are-available-for-cockroachdb-serverless-clusters). When you create a multi-region {{ site.data.products.serverless-plan }} cluster, you will be prompted to select a **Primary region** from which CockroachDB will optimize access to data. If you want to change your region configuration, [you can use the {{ site.data.products.cloud }} Console]({% link cockroachcloud/serverless-cluster-management.md %}#edit-regions), or you can [back up and restore]({% link cockroachcloud/use-managed-service-backups.md %}) your data into a new cluster with the desired configuration.

{{site.data.alerts.callout_info}}
You cannot currently edit the region configuration for a single-region cluster once it has been created, and you cannot remove a region once it has been added.
You cannot currently remove regions once they have been added.
{{site.data.alerts.end}}

For optimal performance, deploy client applications in one of your cluster's configured regions. CockroachDB {{ site.data.products.serverless }} uses a geolocation routing policy to automatically route clients to the nearest region, even if that region is not one of your cluster's configured regions. This means that if you are running an application from a region that is not used by your cluster, connecting to that region may cause high network latency. This may be acceptable for development, but should be avoided for any production or performance-sensitive applications. Refer to the [CockroachDB {{ site.data.products.serverless }} FAQs]({% link cockroachcloud/serverless-faqs.md %}#how-do-i-get-the-sql-endpoint-for-a-specific-region-of-my-multi-region-cluster) for information on overriding the automatic routing policy.
Expand All @@ -66,7 +62,12 @@ Databases created in CockroachDB {{ site.data.products.serverless }} will automa

Storage for a multi-region cluster is billed at the same rate as a single-region cluster. However, by default data is replicated three times in the primary region and once in each additional region, and each replica in the additional regions will accrue more storage costs. For example, a three-region cluster with data replicated five times will use 5/3 times the storage space of a single-region cluster where data is replicated three times.

Cross-region operations will use additional RUs because of the cost of cross-region networking. Cross-region networking costs depend on the source and destination regions. For read operations, the source region contains the replica and the destination region is the gateway region. For write operations, the source region is the gateway region and the destination region is the region containing the replica. There is a network charge for each replica to which the SQL statement writes. Refer to [Pricing](https://www.cockroachlabs.com/pricing) for a matrix of cross-region costs.

Keep in mind the following key points when planning your multi-region CockroachDB {{ site.data.products.serverless }} application's architecture:

- Write-heavy applications may experience a significant increase in RU consumption because replicating writes across all regions consumes more resources.
- Read-heavy applications may experience a smaller increase in RU consumption because the resources required to read from a single region of a multi-region cluster are comparable with a single-region cluster.
- Cross-region reads are an anti-pattern and may significantly increase RU consumption.
- Cross-region writes will also consume additional RUs, but should not significantly increase consumption.
gemma-shay marked this conversation as resolved.
Show resolved Hide resolved

During the multi-region {{ site.data.products.serverless-plan }} [preview](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/cockroachdb-feature-availability#feature-availability-phases), RU usage for queries that cross regions will not account for inter-region bandwidth.