Allow configuring the policy when prewrite encounters lock

[ekexium]

The PR allows the upper layer to control what to do when prewrite encounters lock. A typical usage is for TiDB optimistic autocommit transactions in high-contention scenarios. TiDB will retry the statement in pessimistic mode, so an error can be directly returned to save the effort of backoff, improving efficiency and latency.
A sysbench update_non_index with pareto distribution shows the difference:

If we choose to skip resolving locks when prewrite encounters locks

Throughput:
    events/s (eps):                      1354.3807
    time elapsed:                        300.3328s
    total number of events:              406765

Latency (ms):
         min:                                    0.63
         avg:                                   73.79
         max:                                  582.63
         95th percentile:                      484.44
         sum:                             30015198.03

Master (try resolving locks)

Throughput:
    events/s (eps):                      1172.5760
    time elapsed:                        300.3959s
    total number of events:              352237

Latency (ms):
         min:                                    0.64
         avg:                                   85.23
         max:                                 1028.40
         95th percentile:                      590.56
         sum:                             30019655.50

[you06]

The comparison data between this PR and master in description is same, is there a typo?

[ekexium]

The comparison data between this PR and master in description is same, is there a typo?

Oops. Updated.

[cfzjywxk]

What is the specific design for using the policy at the upper layer? Is it that autocommit optimistic transactions use NoResolvePolicy while everything else remains unchanged?

[ekexium]

autocommit optimistic transactions use NoResolvePolicy while everything else remains unchanged

Yes

[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-11-25 09:18:06.29619009 +0000 UTC m=+455273.915844600: ☑️ agreed by you06.
• 2025-01-02 05:49:19.615761208 +0000 UTC m=+588694.971765771: ☑️ agreed by cfzjywxk.