executor, store/copr: budget merged Analyze batches

[0xTars]

What problem does this PR solve?

Issue Number: ref #67449

Problem Summary:

Full-sampling Analyze batching could multiply physical scan and retained
collector concurrency by the batch width. Merged child execution details could
also be consumed twice: once from child acknowledgements and again from the
outer response.

This draft follows up on #69686 with the bounded-fanout and single-owner
accounting changes found during coordinated review.

What changed and how does it work?

• Negotiate merged data only for full-sampling Analyze requests with
  allow_analyze_batch_task_data_merge.
• Compute a bounded physical scan width as
  min(storeBatchSize + 1, analyzeConcurrency, 5).
• Reduce outer concurrency to
  max(1, floor(analyzeConcurrency / width)), so the physical scan budget
  never exceeds the configured pre-batching Analyze concurrency.
• Treat merged child details as diagnostic and consume the outer aggregate
  once for runtime, runaway-query, and RU accounting.
• Pin the coordinated protocol draft:
  coprocessor: scope batch merge capability to analyze kvproto#1504
• TiKV server/finalizer change:
  coprocessor: specialize batched full-sampling Analyze finalization tikv/tikv#19865

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Validation:

• ./tools/check/failpoint-go-test.sh pkg/executor -run '^TestAnalyzeBatchScanBudget$'
• ./tools/check/failpoint-go-test.sh pkg/store/copr -run '^(TestHandleBatchCopResponseMergedAndUnansweredTasks|TestRUEMA)$'
• ./tools/check/failpoint-go-test.sh pkg/store/copr -race -run '^TestRUEMA$'
• make bazel_prepare
• make lint
• git diff --check

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

Support resource-bounded batching for full-sampling Analyze requests.

[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: 8522bb67-d3bf-4e53-96d3-c6fe7dd017ba

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.

[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 cfzjywxk, mjonss 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

[pingcap-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ 0xPoe
❌ 0xTars
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-tests-checked label, please finished the tests then check the finished items in description.

For example:

Tests <!-- At least one of them must be included. -->

- [x] Unit test
- [ ] Integration test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No code

‼️ Must keep the HTML comments <!-- At least one of them must be included. -->

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}