Skip to content

Modify the introduction of cop_pool_size #21462

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

Merged
merged 2 commits into from
Aug 21, 2025

Conversation

xzhangxian1008
Copy link
Contributor

@xzhangxian1008 xzhangxian1008 commented Jul 25, 2025

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.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot bot added the missing-translation-status This PR does not have translation status info. label Jul 25, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @xzhangxian1008, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the TiFlash configuration documentation by providing a more detailed explanation of the cop_pool_size parameter. The update aims to give users a clearer understanding of how TiFlash manages and processes concurrent coprocessor requests, particularly when the configured pool size is surpassed, by introducing the concept of a rejection threshold.

Highlights

  • Documentation Update: Clarified the behavior of the cop_pool_size parameter in the TiFlash configuration documentation. The updated description now specifies that requests exceeding the cop_pool_size will queue if they are less than 10 times the specified value, and will be rejected if they exceed 10 times the specified value.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ti-chi-bot ti-chi-bot bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 25, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the description for the cop_pool_size configuration parameter in the TiFlash documentation. I've suggested a rephrasing to improve clarity and readability, making the queuing and rejection logic easier to understand.

@qiancai qiancai self-assigned this Jul 25, 2025
@qiancai qiancai added translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. and removed missing-translation-status This PR does not have translation status info. labels Jul 25, 2025
Copy link
Contributor

@windtalker windtalker left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link

ti-chi-bot bot commented Jul 25, 2025

@windtalker: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link
Collaborator

@qiancai qiancai left a comment

Choose a reason for hiding this comment

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

Rest LGTM

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Aug 21, 2025
Copy link

ti-chi-bot bot commented Aug 21, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-08-21 04:05:18.724015726 +0000 UTC m=+499126.667191242: ☑️ agreed by qiancai.

@qiancai qiancai added the needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. label Aug 21, 2025
@qiancai
Copy link
Collaborator

qiancai commented Aug 21, 2025

/approve

@qiancai qiancai added the lgtm label Aug 21, 2025
Copy link

ti-chi-bot bot commented Aug 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Aug 21, 2025
@qiancai qiancai added area/bigdata Indicates that the Issue or PR belongs to the area of TiFlash, TiSpark, and OLAP. and removed approved labels Aug 21, 2025
@ti-chi-bot ti-chi-bot bot added the approved label Aug 21, 2025
Copy link

ti-chi-bot bot commented Aug 21, 2025

@qiancai: You cannot manually add or delete the cherry pick approval state labels, only I and the tursted members have permission to do so. You can approve it in internal platform.

In response to removing label named approved.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@qiancai qiancai added the type/enhancement The issue or PR belongs to an enhancement. label Aug 21, 2025
@ti-chi-bot ti-chi-bot bot merged commit b561c2e into pingcap:master Aug 21, 2025
9 checks passed
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-8.5: #21627.

breezewish added a commit that referenced this pull request Aug 21, 2025
…auto-embed

* commit 'b570cc86270ba2e2b2b71d6eab8d717c2c8a1c56': (48 commits)
  *: remove TiDB roadmap from TOC, home, index, add warning (#21628) (#21637)
  Update the scope of system-variable ”tidb_redact_log“ (#21513) (#21634)
  *: add custom Japanese localization for cloud docs (#21612)
  Modify the introduction of `cop_pool_size` (#21462) (#21627)
  tiflash: Update tiflash upgrade guide (#21619) (#21625)
  Update tidb-performance-tuning-config.md (#21621) (#21624)
  Update tidb-cloud-poc.md (#21336) (#21411)
  cloud: update the pricing link for starter  (#21620)
  ticdc: clarify descriptions of `index-value` and `columns` (#21616) (#21617)
  release-8.5: remove 'v' prefix from tidb-version variable (#21614)
  release-8.5: update version to 8.5.3 (#21613)
  cloud: fix note annotation syntax for proper rendering (#21611)
  ticdc: add key word for redo log (#21564) (#21607)
  ticdc: correct the tiup cluster command (#21135) (#21608)
  bump TiDB from v8.5.2 to v8.5.3 (#21578)
  v8.5.3: add release notes (#21399) (#21606)
  v8.5.3: log backup: update metafile format (#21412) (#21577)
  v8.5.3: update telemetry related doc files (#21404) (#21603)
  system-variables: add optimizer cost factors (#20748) (#21602)
  Add more description about SHARD_ROW_ID_BITS (#21467) (#21600)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved area/bigdata Indicates that the Issue or PR belongs to the area of TiFlash, TiSpark, and OLAP. lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants