copr: Fix bug that mpp node availability detect does not work in some corner cases (#28201)

[ti-srebot]

cherry-pick #28201 to release-5.2
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/28289

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/28289:release-5.2-624f7cab3b4e

---

What problem does this PR solve?

Issue Number: close pingcap/tiflash#3118

Problem Summary:
As described in the issue.

What is changed and how it works?

Proposal: xxx

What's Changed:

How it Works:
The root cause is we detect the TiFlash node's availability in balanceBatchCopTask, but here is a shortcut in balanceBatchCopTask that if there is only one batchCopTask, it will return directly without balancing, which means the availability check is also skipped.

tidb/store/copr/batch_coprocessor.go

Lines 107 to 111 in 3c9c01e

	func balanceBatchCopTask(ctx context.Context, kvStore *kvStore, originalTasks []*batchCopTask, mppStoreLastFailTime map[string]time.Time, ttl time.Duration) []*batchCopTask {
	if len(originalTasks) <= 1 {
	return originalTasks
	}
	isMPP := mppStoreLastFailTime != nil

This pr fix this by not trigger the shortcut if the query is mpp query.

Check List

Tests

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

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

Fix bug that mpp node availability detect does not work in some corner cases

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• fzhedu
• hanfei1991

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 submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@windtalker you're already a collaborator in bot's repo.

[fzhedu]

/LGTM

[fzhedu]

/merge

[ti-chi-bot]

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

Commit hash: a422efe

[ti-chi-bot]

@ti-srebot: 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.