server: exit tidb-server directly when all connections not in txn (#44953)

[bb7133]

This is a manual backport of #44953:

---

What problem does this PR solve?

Issue Number: close #44951

Problem Summary: After #32111, user need to wait for all connections to be disconnected, or execute a new sql before tidb-server exit. It's not an expected behaviour.

What is changed and how it works?

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.

Exit tidb-server directly when all connections not in txn

[Defined2014]

/retest

[purelind]

The branch naming tidb-6.5-with-kv-timeout-feature is not in the correct format. I will handle the triggering of this branch separately.

[purelind]

/test ?

[ti-chi-bot]

@purelind: The following commands are available to trigger required jobs:

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

Use /test all to run all jobs.

In response to this:

/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]

@purelind: No presubmit jobs available for pingcap/tidb@tidb-6.5-with-kv-timeout-feature

In response to this:

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

[bb7133]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crazycs520, Defined2014

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:

• OWNERS [Defined2014,crazycs520]

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-12-15 01:50:34.256287029 +0000 UTC m=+580125.293513956: ☑️ agreed by Defined2014.
• 2023-12-19 09:02:47.017420924 +0000 UTC m=+951658.054647851: ☑️ agreed by crazycs520.

[hawkingrei]

/retest

[ti-chi-bot]

@bb7133: 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/unit-test	743a51e	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	743a51e	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev_2	743a51e	link	true	/test check-dev2

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.