Skip to content

Comments

sessionctx: Increase max value for innodb_lock_wait_timeout#65153

Merged
ti-chi-bot[bot] merged 3 commits intopingcap:masterfrom
dveeden:max_lock_wait_timeout
Dec 22, 2025
Merged

sessionctx: Increase max value for innodb_lock_wait_timeout#65153
ti-chi-bot[bot] merged 3 commits intopingcap:masterfrom
dveeden:max_lock_wait_timeout

Conversation

@dveeden
Copy link
Contributor

@dveeden dveeden commented Dec 21, 2025

What problem does this PR solve?

Issue Number: close #65152

Problem Summary:

What changed and how does it work?

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

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-triage-completed release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/needs-tests-checked size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 21, 2025
@tiprow
Copy link

tiprow bot commented Dec 21, 2025

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

Details

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-sigs/prow repository.

@dveeden dveeden requested review from AilinKid and mjonss December 21, 2025 11:41
@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Dec 21, 2025
@codecov
Copy link

codecov bot commented Dec 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.6928%. Comparing base (969d090) to head (b362cbe).
⚠️ Report is 7 commits behind head on master.

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     
Flag Coverage Δ
integration 41.6796% <100.0000%> (-6.4906%) ⬇️
unit 65.9671% <100.0000%> (+0.4483%) ⬆️

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

Components Coverage Δ
dumpling 52.8700% <ø> (ø)
parser ∅ <ø> (∅)
br 38.6566% <ø> (-19.5603%) ⬇️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@mjonss mjonss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Dec 22, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 22, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-12-21 11:41:28.929286042 +0000 UTC m=+1991633.743063614: ☑️ agreed by lance6716.
  • 2025-12-22 09:54:59.950197049 +0000 UTC m=+2071644.763974631: ☑️ agreed by mjonss.

Copy link

@yudongusa yudongusa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please open a document PR on this.

@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 22, 2025

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dveeden
Copy link
Contributor Author

dveeden commented Dec 22, 2025

Please open a document PR on this.

pingcap/docs#22212

@ti-chi-bot ti-chi-bot bot merged commit 9c74029 into pingcap:master Dec 22, 2025
29 checks passed
dveeden added a commit to dveeden/hibernate-orm that referenced this pull request Feb 13, 2026
- 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
dveeden added a commit to dveeden/hibernate-orm that referenced this pull request Feb 16, 2026
- 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
dveeden added a commit to dveeden/hibernate-orm that referenced this pull request Feb 18, 2026
- 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Max value for innodb_lock_wait_timeout is differs from MySQL

4 participants