tikv: distinguish server timeout for TiKV and TiFlash

[LittleFall]

What problem does this PR solve?

This pr is a follow-up of #21109

Problem Summary: Some TiFlash server time out still show TiKV server timeout.

What is changed and how it works?

What's Changed:

Fix it in batch cop requests.

Related changes

• PR to update pingcap/docs/pingcap/docs-cn: no
• Need to cherry-pick to the release branch: no, master/5.0's issue has been fixed in store/copr: polish the tiflash-tikv fallback function. #23078

Check List

Tests

• Integration test
• Manual test (add detailed scripts or steps below)

create table t(a int);
alter table t set tiflash replica 1;
-- let TiFlash hang, for example, pause it while debugging.
explain analyze select * from t; -- cop
[HY000][9012] TiFlash server timeout
explain analyze select count(*) from t; -- batch, before this pr, it's [9002] TiKV server timeout
[HY000][9012] TiFlash server timeout

Side effects

Release note

• Fix a bug that causes TiDB to report TiKV server timeout when executing TiFlash batch request.

[LittleFall]

/run-check_dev

[LittleFall]

/run-all-tests

[LittleFall]

/cc @hanfei1991 , @lzmhhh123

[LittleFall]

/cc @hanfei1991

[LittleFall]

/cc @lzmhhh123

[djshow832]

Can you add some test cases?

[djshow832]

/lgtm

[LittleFall]

/label type/bug-fix

[ti-chi-bot]

@LittleFall: The label(s) type/bug-fix cannot be applied. These labels are supported: CHANGELOG, challenge-program, compatibility-breaker, contribution, correctness, first-time-contributor, good-first-issue, hacktoberfest, high-performance, hptc, need-more-info, needs-cherry-pick-3.0, needs-cherry-pick-3.1, needs-cherry-pick-4.0, needs-cherry-pick-5.0-rc, needs-cherry-pick-5.0, proposal, release-note, require-LGT3, security, tools.

In response to this:

/label type/bug-fix

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.

[LittleFall]

/type bug-fix

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• djshow832
• lzmhhh123

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[lzmhhh123]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: a4f83b5

[LittleFall]

/label cherry-pick-approved

[ti-chi-bot]

@LittleFall: The label(s) cherry-pick-approved cannot be applied. These labels are supported: CHANGELOG, challenge-program, compatibility-breaker, contribution, correctness, first-time-contributor, good-first-issue, hacktoberfest, high-performance, hptc, need-more-info, needs-cherry-pick-3.0, needs-cherry-pick-3.1, needs-cherry-pick-4.0, needs-cherry-pick-5.0-rc, needs-cherry-pick-5.0, proposal, release-note, require-LGT3, security, tools.

In response to this:

/label cherry-pick-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.

[djshow832]

/cc @zhouqiang-cl

[ti-chi-bot]

@LittleFall: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what's changed

Or if the count of mainly changed packages are more than 3, use

• *: what's changed