Repository navigation
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: 🔵 Low · up to
|
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
- Configuration used: Repository: pingcap/docs/.coderabbit.yaml
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
c63c970f-9949-49f7-93ee-1b4eae5edc51
📒 Files selected for processing (3)
tidb-cloud/architecture-concepts.mdtidb-cloud/create-tidb-cluster-serverless.mdtidb-cloud/premium/create-tidb-instance-premium.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
| - For {{{ .essential }}} instances running CLOUD.202603.x or later, **Elastic Mode** is selected by default. In Elastic Mode, you do not set a maximum RCU. Instead, your instance uses a fixed **Baseline RCU** of 2,000 RCUs, which is the minimum number of Request Capacity Units (RCUs) you are billed for and the initial capacity for autoscaling. | ||
|
|
||
| - RCUs represent the compute resources provisioned for your workload. TiDB Cloud automatically scales your {{{ .essential }}} instance within this range based on demand. | ||
| - For {{{ .essential }}} instances on earlier versions, use **Max RCU Compatibility Mode**, and specify both a minimum and maximum number of RCUs for the instance. |
There was a problem hiding this comment.
| - For {{{ .essential }}} instances on earlier versions, use **Max RCU Compatibility Mode**, and specify both a minimum and maximum number of RCUs for the instance. | |
| - For {{{ .essential }}} instances running on TiDB v8.5.3 or earlier versions, only **Max RCU Compatibility Mode** is supported, and you need to specify both a minimum and maximum number of RCUs for the instance. |
Reason: "Use" suggests that users can select the capacity mode for earlier versions. If the mode is determined by the instance version, describe it as the applicable mode instead.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
First-time contributors' checklist
What is changed, added, or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit