executor, store/copr: batch full-sampling Analyze requests

[0xTars]

What problem does this PR solve?

Issue Number: ref #70059

Problem Summary:

Full-sampling Analyze sends many region coprocessor requests. Store batching can reduce RPC overhead, but the client and store need an explicit merged-result contract, complete per-task resource accounting, and a concurrency budget that does not multiply the existing Analyze DistSQL or system-process scan limit by the batch width.

This replaces #69686 because its source branch cannot be updated. Issue #70059 tracks this batching design; #67449 is related sample-based NDV work, not the design source for this PR.

What changed and how does it work?

• Group compatible full-sampling Analyze region tasks by store and send them through StoreBatchTasks.
• Opt in to the kvproto merged-result contract from coprocessor: negotiate merged batch task data kvproto#1511 and consume each child acknowledgment by its unique task ID.
• Use resourcecontrol: settle batched cop tasks' execution details tikv/client-go#2032 so scan bytes and KV CPU from every attached batch response participate in resource-control settlement.
• Derive batching from the already-resolved Analyze scan budget C: width = min(C, 5), outer concurrency C / width, and width - 1 child tasks. Therefore total logical scan concurrency remains at most C for both manual Analyze and restricted/system Analyze.
• Keep the package test count at the repository limit by grouping the two related batch-response scenarios into one behavior suite; update the existing executor/store test case maps.

Related replacement chain:

• coprocessor: negotiate merged batch task data kvproto#1511
• coprocessor: merge batched full-sampling results tikv/tikv#19871
• resourcecontrol: settle batched cop tasks' execution details tikv/client-go#2032

Check List

Tests

• Unit test
  • ./tools/check/failpoint-go-test.sh pkg/executor -run '^TestAnalyzeBatchScanBudget$' -count=1
  • ./tools/check/failpoint-go-test.sh pkg/store/copr -run '^TestHandleBatchCopResponse$' -count=1
  • ./tools/check/failpoint-go-test.sh pkg/store/copr/copr_test -run '^TestBuildCopIteratorWithBatchStoreCopr$' -count=1
  • make lint
  • make bazel_prepare (zero generated diff)
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Reduce full-sampling ANALYZE RPC overhead while keeping total logical scan concurrency within the Analyze scan budget.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7fbe3a46-0d8a-4c1d-b612-f6378c4cf420

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ti-chi-bot]

Hi @0xTars. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[pingcap-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign 0xpoe, cfzjywxk for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS
• pkg/distsql/OWNERS
• pkg/executor/OWNERS

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