txn: fix issue innodb_lock_wait_timeout doesn't work in some case

[crazycs520]

What problem does this PR solve?

Issue Number: close #56688

Problem Summary: fix issue innodb_lock_wait_timeout doesn't work when tikv always return WriteConflict error.

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

[tiprow]

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

[crazycs520]

/retest

[tiprow]

@crazycs520: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.2565%. Comparing base (71238b1) to head (a88b05f).
Report is 343 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56847         +/-   ##
=================================================
- Coverage   73.3327%   57.2565%   -16.0762%     
=================================================
  Files          1636       1791        +155     
  Lines        453537     642871     +189334     
=================================================
+ Hits         332591     368086      +35495     
- Misses       100560     249692     +149132     
- Partials      20386      25093       +4707     

Flag	Coverage Δ
integration	39.6353% <15.7894%> (?)
unit	72.6781% <100.0000%> (+0.1395%)	⬆️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	63.0957% <ø> (+17.0790%)	⬆️

[crazycs520]

/retest-required

[tiprow]

@crazycs520: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest-required

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.

[crazycs520]

/retest-required

[tiprow]

@crazycs520: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest-required

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, you06

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 [cfzjywxk,you06]

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-10-28 09:21:21.794581375 +0000 UTC m=+255194.633736920: ☑️ agreed by cfzjywxk.
• 2024-10-28 10:11:47.036935708 +0000 UTC m=+258219.876091250: ☑️ agreed by you06.

[cfzjywxk]

/retest

[tiprow]

@cfzjywxk: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[cfzjywxk]

/ok-to-test

[cfzjywxk]

/retest

[cfzjywxk]

/test check-dev2

[tiprow]

@cfzjywxk: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test fast_test_tiprow_ddlargsv1
• /test tidb_parser_test

Use /test all to run the following jobs that were automatically triggered:

• fast_test_tiprow
• tidb_parser_test

In response to this:

/test check-dev2

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.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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