operator: pause scheduler after all connections established

[YuJuncen]

What problem does this PR solve?

Issue Number: ref #51448

Problem Summary:

In #51449, we delayed pausing admin commands after all connections are established. But that isn't enough, due to PD schedulers are paused and ID allocation is disabled.

What changed and how does it work?

This PR pauses PD's scheduler after all connections are established.

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

[tiprow]

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

[codecov]

Codecov Report

Merging #51823 (68933ec) into master (4d4f438) will decrease coverage by 16.7791%.
Report is 96 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51823         +/-   ##
=================================================
- Coverage   72.4345%   55.6554%   -16.7791%     
=================================================
  Files          1476       1587        +111     
  Lines        364442     621175     +256733     
=================================================
+ Hits         263982     345718      +81736     
- Misses        80976     251964     +170988     
- Partials      19484      23493       +4009     

Flag	Coverage Δ
integration	38.4863% <100.0000%> (?)
unit	70.4850% <18.7500%> (-1.8264%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (-2.3014%)	⬇️
parser	∅ <ø> (∅)
br	51.7381% <100.0000%> (+5.3608%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, Leavrth

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/OWNERS [BornChanger,Leavrth]

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:

• 2024-03-25 03:25:20.983199011 +0000 UTC m=+1865548.005445398: ☑️ agreed by BornChanger.
• 2024-03-25 08:17:51.094793306 +0000 UTC m=+1883098.117039695: ☑️ agreed by Leavrth.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[nkg-]

release-6.5 cherrypick was closed without merging. #52068.

[nkg-]

Oh. Seems like it was pulled into release6.5 via #51730