Skip to content

Conversation

peachdawnleach
Copy link
Contributor

Addresses: DOC-14350

Changed: Added line to show lack of support for 2vcpu clusters

Added line to show lack of support for 2vcpu clusters
Copy link

Copy link

netlify bot commented Aug 13, 2025

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit 534cdb5
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/689e383d4d653a000898b6e4

Copy link

netlify bot commented Aug 13, 2025

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit 534cdb5
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/689e383da0d717000826916a

Copy link

netlify bot commented Aug 13, 2025

Netlify Preview

Name Link
🔨 Latest commit 5a71717
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/689ccfd2e01e67000883a0ee
😎 Deploy Preview https://deploy-preview-20119--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

netlify bot commented Aug 13, 2025

Netlify Preview

Name Link
🔨 Latest commit 534cdb5
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/689e383d392de000089fef15
😎 Deploy Preview https://deploy-preview-20119--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@peachdawnleach peachdawnleach requested a review from jhlodin August 13, 2025 18:07
@@ -40,7 +40,7 @@ If your cluster's workload is subject to [compliance]({% link cockroachcloud/com

A cluster's number of nodes and node capacity together determine the node's total compute and storage capacity.

When considering your cluster's scale, we recommend that you start by planning the compute requirements per node. If a workload requires more than 16 vCPUs per node, consider adding more nodes. For example, if a 3-node cluster with 8 vCPUs per node is not adequate for your workload, consider scaling up to 16 vCPUs before adding a fourth node. For most production applications, we recommend at minimum 8 vCPUs per node.
When considering your cluster's scale, we recommend that you start by planning the compute requirements per node. If a workload requires more than 16 vCPUs per node, consider adding more nodes. For example, if a 3-node cluster with 8 vCPUs per node is not adequate for your workload, consider scaling up to 16 vCPUs before adding a fourth node. For most production applications, we recommend at minimum 8 vCPUs per node. We do not provide support for clusters with only 2 vCPUs per node.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this note is better served as a warning banner below this paragraph, given that it came up frequently enough that PM requested an explicit callout.

You can search the docs for instances of site.data.alerts.callout_danger for the syntax for this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok will do!

Moved information to warning block
@peachdawnleach
Copy link
Contributor Author

Screenshot of how the change will look on the docs site:
Screenshot 2025-08-13 at 4 57 47 PM

Copy link
Contributor

@jhlodin jhlodin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM pending one nit and PM review

When considering your cluster's scale, we recommend that you start by planning the compute requirements per node. If a workload requires more than 16 vCPUs per node, consider adding more nodes. For example, if a 3-node cluster with 8 vCPUs per node is not adequate for your workload, consider scaling up to 16 vCPUs before adding a fourth node. For most production applications, we recommend at minimum 8 vCPUs per node.

{{site.data.alerts.callout_danger}}
We do not provide support for clusters with only 2 vCPUs per node.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed offline - we ought to be very particular about if/when to use 'we' in this context, and in this case because it is a support policy in the contract I think this should say 'Cockroach Labs does not provide support... '

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed

@peachdawnleach peachdawnleach enabled auto-merge (squash) August 14, 2025 18:52
@peachdawnleach peachdawnleach merged commit c400a46 into main Aug 14, 2025
5 checks passed
@peachdawnleach peachdawnleach deleted the 20250812-DOC-14350-2vcpu-clusters branch August 14, 2025 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants