copr: support choose non pending tiflash peer when dispatch MPPTask

[guo-shaoge]

What problem does this PR solve?

Issue Number: close #44221

Problem Summary: As issue said, we want to consider tiflash replica pending status when dispatch MPPTask

What is changed and how it works?

1. Support get pending tiflash peer store, most changes are in region_cache: support check pending tiflash peer tikv/client-go#821
2. Choose nonPending stores as balance candidate, otherwise use allStores.

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

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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

[guo-shaoge]

Wait tikv/client-go#821 merge first

[disksing]

they are always equal because they are the same slice.

[ti-chi-bot]

PR needs rebase.

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/test-infra 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 ask for approval from guo-shaoge. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[guo-shaoge]

will fix later

[tiprow]

@guo-shaoge: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tiprow_fast_test	af9318c	link	true	/test tiprow_fast_test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[ti-chi-bot]

@guo-shaoge: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/mysql-test	af9318c	link	true	/test mysql-test
pull-mysql-client-test	af9318c	link	true	/test pull-mysql-client-test
idc-jenkins-ci-tidb/check_dev_2	af9318c	link	true	/test check-dev2
pull-integration-ddl-test	af9318c	link	true	/test pull-integration-ddl-test
idc-jenkins-ci-tidb/build	af9318c	link	true	/test build
idc-jenkins-ci-tidb/check_dev	af9318c	link	true	/test check-dev
idc-jenkins-ci-tidb/unit-test	af9318c	link	true	/test unit-test
pull-br-integration-test	af9318c	link	true	/test pull-br-integration-test
pull-lightning-integration-test	af9318c	link	true	/test pull-lightning-integration-test
pull-integration-e2e-test	af9318c	link	true	/test pull-integration-e2e-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.