session: lower innodb-lock-wait-timeout MaxValue to match max-txn-ttl

[Alkaagr81]

What problem does this PR solve?

Issue Number: close #33472

Problem Summary: innodb_lock_wait_timeout can exceed max-txn-ttl

What is changed and how it works?

The Innodb-Lock-Wait-Timeout max value is changed to 3600 which converts to 3600000 MS, the same as max-txn-ttl default.

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
  Minimal change to MySQL compatibility: most users don't change this setting, and setting it to a larger value results in a warning + truncation, not an error.

Release note

The maximum value for the system variable innodb_lock_wait_timeout has been lowered to 3600 seconds. This matches the max-txn-ttl.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• morgo
• ngaut

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.

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[Alkaagr81]

/run-check_title

[Alkaagr81]

/cc @morgo

[morgo]

/run-unit-test

[morgo]

LGTM

[ngaut]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 3ac41f3

[hawkingrei]

/check-issue-triage-complete

[ti-chi-bot]

@Alkaagr81: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.

[hawkingrei]

/run-mysql-test

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/2f7f4f34e54e52e59b8a3ca22ec259bacafaeb79