sessionctx: Increase max value for innodb_lock_wait_timeout#65153
sessionctx: Increase max value for innodb_lock_wait_timeout#65153ti-chi-bot[bot] merged 3 commits intopingcap:masterfrom
Conversation
|
Hi @dveeden. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. DetailsInstructions 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. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #65153 +/- ##
================================================
- Coverage 70.7525% 68.6928% -2.0597%
================================================
Files 1895 1873 -22
Lines 518076 510928 -7148
================================================
- Hits 366552 350971 -15581
- Misses 127017 137608 +10591
+ Partials 24507 22349 -2158
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
yudongusa
left a comment
There was a problem hiding this comment.
Please open a document PR on this.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lance6716, mjonss, yudongusa The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
- In MySQL `innodb_lock_wait_timeout` can be between 1 and 1073741824 - In TiDB v8.5.5 `innodb_lock_wait_timeout` can be between 1 and 3600 - In TiDB maste `innodb_lock_wait_timeout` can be between 1 and 1073741824 This PR adds an argument to `ConnectionLockTimeoutStrategyImpl` to set the limit of the `innodb_lock_wait_timeout` so it can be re-used by TiDB v8.5.5 References: - https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_innodb_lock_wait_timeout - https://docs.pingcap.com/tidb/stable/system-variables/#innodb_lock_wait_timeout - pingcap/tidb#65153
- In MySQL `innodb_lock_wait_timeout` can be between 1 and 1073741824 - In TiDB v8.5.5 `innodb_lock_wait_timeout` can be between 1 and 3600 - In TiDB maste `innodb_lock_wait_timeout` can be between 1 and 1073741824 This PR adds an argument to `ConnectionLockTimeoutStrategyImpl` to set the limit of the `innodb_lock_wait_timeout` so it can be re-used by TiDB v8.5.5 References: - https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_innodb_lock_wait_timeout - https://docs.pingcap.com/tidb/stable/system-variables/#innodb_lock_wait_timeout - pingcap/tidb#65153
- In MySQL `innodb_lock_wait_timeout` can be between 1 and 1073741824 - In TiDB v8.5.5 `innodb_lock_wait_timeout` can be between 1 and 3600 - In TiDB maste `innodb_lock_wait_timeout` can be between 1 and 1073741824 This PR adds an argument to `ConnectionLockTimeoutStrategyImpl` to set the limit of the `innodb_lock_wait_timeout` so it can be re-used by TiDB v8.5.5 References: - https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_innodb_lock_wait_timeout - https://docs.pingcap.com/tidb/stable/system-variables/#innodb_lock_wait_timeout - pingcap/tidb#65153 Co-authored-by: Christian Beikov <christian.beikov@gmail.com>
What problem does this PR solve?
Issue Number: close #65152
Problem Summary:
What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.