*: fix grpc client leak bug for AUTO_ID_CACHE=1 tables

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #48869

Problem Summary:

What changed and how does it work?

Prior to this commit, each auto id allocator has it's own autoid client (a grpc connection inside), so if we have 60K tables there would be 60K tcp connections ...

After the fix, the autoid client is moved to domain so there should be only one autoid client instance. All the autoid allocator share this instance now.

Check List

Tests

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

See the reproduce steps in the issue.
The test check tcp connection counts, it's harder to do that in unit test

• 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.

Fix grpc client leak bug for AUTO_ID_CACHE=1 tables, this bug is more likely to happen when there are lots of tables, and the error message is "connect: cannot assign requested address"

[tiprow]

Hi @tiancaiamao. 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/test-infra repository.

[tiancaiamao]

A similiar leaky issue of etcd client on AUTO_ID_CACHE=1 tables, but this time it's the grpc client leak.
Ref #46324

[codecov]

Codecov Report

Merging #48870 (6943f31) into master (67b70e5) will decrease coverage by 17.4265%.
Report is 19 commits behind head on master.
The diff coverage is 71.4285%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #48870         +/-   ##
=================================================
- Coverage   71.0203%   53.5939%   -17.4265%     
=================================================
  Files          1366       1587        +221     
  Lines        404643     597920     +193277     
=================================================
+ Hits         287379     320449      +33070     
- Misses        97264     254972     +157708     
- Partials      20000      22499       +2499     

Flag	Coverage Δ
integration	35.1412% <71.0526%> (?)
unit	71.1038% <42.8571%> (+0.0835%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	55.4750% <50.0000%> (+2.4651%)	⬆️

[tangenta]

Maybe it is more efficient to reuse etcdCli and autoidCli globally. We can improve this in another PR. /cc @D3Hunter

[tangenta]

@tiancaiamao Is there any plan to refine the retry logic?

[tiancaiamao]

/test unit-test

[tiancaiamao]

/test unit-test

[ti-chi-bot]

@tiancaiamao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test canary-notify-when-compatibility-sections-changed
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-ddl-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-mysql-client-test
• /test pull-sqllogic-test
• /test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test unit-test

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]

@tiancaiamao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

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.

[tangenta]

/retest

[tiprow]

@tangenta: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 APPROVED

This pull-request has been approved by: lance6716, tangenta

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

The pull request process is described here

Needs approval from an approver in each of these files:

• br/pkg/lightning/OWNERS [lance6716]
• pkg/ddl/OWNERS [tangenta]
• pkg/disttask/OWNERS [lance6716,tangenta]
• pkg/domain/OWNERS [lance6716,tangenta]
• pkg/meta/OWNERS [tangenta]

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]

[LGTM Timeline notifier]

Timeline:

• 2023-11-24 06:42:03.791910568 +0000 UTC m=+559352.457136764: ☑️ agreed by tangenta.
• 2023-11-24 09:08:10.501152106 +0000 UTC m=+568119.166378301: ☑️ agreed by lance6716.

[tiancaiamao]

/test unit-test

[tiprow]

@tiancaiamao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

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]

In response to a cherrypick label: new pull request created to branch release-7.1: #48891.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #48892.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #48893.