lightning: try balance lighting throughput to all tikvs(consider all peers)

[guoshouyan]

previously PR: #54615
in previous PR, it only consider leader region store id when trying to balance throughput to all tikv. In this PR, I try to consider all peers

1. first have the struct RangeAndRegion to store both the range and its regions information
2. have a map regionProcessingMap := sync.Map{} to stores all store id that are currently importing. when we assign a range to a worker, we increase the count. When the range finishes, we decrease the count.
3. in pickRanges, it will find the best range to import. It iterates through all ranges and calculate a score: sum(number of current region importing). And we always try to schedule the one with lowest score.

perform testing: importing about 10T data with 7 lightning on a cluster with 30 tikv nodes and store limit of 30MB

1. without pre split(base line): time taken 130 mins, throughput about 666 MB/s per lightning
   
   

2. with presplit: time taken more than 3 hours, killed. throughput below 300 MB/s
   
   

3. with presplit and balance across leader region store id: time taken 160 mins, throughput 512 MB/s
   
   

4. with presplit and balance across all peer store id: time take 100 mins, throughput around 800~1000 MB/s
   
   

What problem does this PR solve?

Issue Number: ref #56113

Problem Summary:

What changed and how does it work?

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.

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

[sre-bot]

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.

✅ guoshouyan
❌ shouyan.guo

---

shouyan.guo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{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 bb7133 for approval. For more information see the 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

[ti-chi-bot]

Hi @guoshouyan. 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.

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.

[tiprow]

Hi @guoshouyan. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[lance6716]

/ok-to-test

[lance6716]

passing processingRegions to writeAndIngestByRange in line 1722, to skip the inner scan region API in line 1470?

[ti-chi-bot]

@guoshouyan: 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/check_dev	b862c36	link	true	/test check-dev
idc-jenkins-ci-tidb/check_dev_2	b862c36	link	true	/test check-dev2
idc-jenkins-ci-tidb/mysql-test	b862c36	link	true	/test mysql-test
idc-jenkins-ci-tidb/unit-test	b862c36	link	true	/test unit-test
idc-jenkins-ci-tidb/build	b862c36	link	true	/test build

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.